# elizaOS Discord - 2025-03-17

## Overall Discussion Highlights

### ElizaOS V2 Development
- V2 beta has been released with full launch planned for the end of March
- Websockets functionality was recently added to improve web interface connections
- Some users have successfully implemented V2, with one user (Jungle) offering direct help via DM
- The development team is working on plugin auto-updating for V2
- Several users reported issues with the Twitter client in the latest version

### Technical Implementation Challenges
- RAG (Retrieval-Augmented Generation) implementation issues with PDF files requiring proper directory structure and "enableRag: true" setting
- Plugin installation challenges, particularly with the paradex plugin
- Directory path issues with knowledge folders needing to be directly under ./knowledge, not ./characters/knowledge
- Version mismatches between npm packages (0.25.6-alpha vs 0.25.9) causing compatibility problems
- TEXT_EMBEDDING model errors in core-runtime initialization

### Community Organization & Governance
- A new dao-organization channel was created as a grassroots effort to strengthen ElizaDAO's governance
- Vincent proposed creating a directory of partners organized by specialties to better utilize community talent
- Jin shared technical resources including GitHub repositories and analytics on Discord and GitHub contributors
- The community discussed implementing an "AI Jedi Council" with 12 agent personas representing different aspects of the DAO
- Proposal to create simpler onboarding for community members who aren't as familiar with AI tools

### Token Economics & Utility
- Community members expressed concerns about the lack of clear tokenomics documentation
- Suggestions to use ai16z tokens to pay for API and compute on agents
- Questions about whether the team has tokenomics experts who understand feedback loops
- References to a hackmd document containing tokenomics information, though some found it confusing
- Mentions of token price decline, with references to a 70% drop from previous highs

### Marketing & Communication
- Significant tension between some partners and the team regarding communication strategy
- Zolo provided detailed marketing suggestions, highlighting missed opportunities for co-marketing
- Jin mentioned focusing on "product first, then whitepaper" approach
- Ben acknowledged feedback and announced that social/brand will be the primary focus after the GTM for the launchpad
- Discussion about better coordination of social media engagement and reposting community content

## Key Questions & Answers

**Q: When is V2 coming out?**  
A: V2 beta is out now, with full launch planned for the end of the month (answered by shaw)

**Q: What does elizaOS do or will do?**  
A: elizaOS is building a platform for AI agents that can talk to each other and help humans, making it easy to create, customize and deploy AI assistants without coding (answered by jintern)

**Q: Where can I find tokenomics information?**  
A: The notes are available at https://hackmd.io/@xr/ai16z-tokenomics (answered by jin)

**Q: What is the reason the agent sometimes responds two times?**  
A: It can be controlled with "suppressInitialMessage":true in your action (answered by notorious_d_e_v)

**Q: Will v2.0 have direct API/websocket access to connect agents to website chat terminals?**  
A: Yes, Shaw just added websockets functionality which allows connecting agents to web interfaces (answered by jin/jintern)

**Q: Is there any utility for ai16z partners NFT?**  
A: Not afaik but it's not our project and belongs to https://x.com/partnersDAO/ (answered by Patt)

**Q: What is the goal of this DAO-organization working group?**  
A: To unite the growing ecosystem and create clear pathways for meaningful contribution to build open-AGI (answered by vincentpaul)

**Q: Has anyone here successfully got V2 running?**  
A: I got it running, DM if you want (answered by Jungle)

## Community Help & Collaboration

1. **RAG Implementation Help**
   - Helper: jin/jintern
   - Issue: User struggling with RAG directory errors and PDF file implementation
   - Resolution: Explained that knowledge directories should be directly under ./knowledge folder and advised enabling RAG explicitly with "enableRag": true

2. **Plugin Installation Support**
   - Helper: 🧧ThanosDaSith24🧧
   - Issue: User having trouble installing paradex plugin
   - Resolution: Provided correct installation command using npx elizaos plugins add format

3. **Agent Response Behavior**
   - Helper: notorious_d_e_v
   - Issue: Agent responding twice to messages
   - Resolution: Suggested using "suppressInitialMessage":true in action to prevent double responses

4. **Community Organization**
   - Helper: jin
   - Issue: Need for better documentation of ElizaDAO resources
   - Resolution: Shared links to GitHub repos, HackMD newsletters, and eliza.how/news

5. **V2 Implementation**
   - Helper: Jungle
   - Issue: Users struggling to implement V2
   - Resolution: Offered direct help via DM after successfully implementing it

6. **Documentation Site Fix**
   - Helper: BKKev
   - Issue: Documentation site (eliza.how) configuration issue
   - Resolution: Issue was fixed by admins

## Action Items

### Technical Tasks
1. Complete V2 development and prepare for full launch (Mentioned by shaw)
2. Fix Twitter client integration in latest ElizaOS version (Mentioned by bradtheaverage)
3. Fix image generation posting with Twitter (Mentioned by Abderahman)
4. Implement plugin auto-updating (Mentioned by shaw)
5. Fix paradex plugin build errors (Mentioned by fiend)
6. Fix version mismatch in @elizaos/cli for plugin-sql dependency (Mentioned by Gabriel)
7. Fix TEXT_EMBEDDING model errors in core-runtime initialization (Mentioned by chris.troutner)
8. Update jintern AI assistant to V2 (Mentioned by jin)
9. Create a privacy-preserving directory of partners and agents with their specialties (Mentioned by vincentpaul)
10. Implement an "AI Jedi Council" with 12 agent personas representing different aspects of the DAO (Mentioned by jin)
11. Evaluate feedback loops for tokenomics plan viability (Mentioned by Patt)
12. Update all client packages (telegram, twitter, discord) to version 0.25.9 on npm (Mentioned by Royal Lobster)

### Documentation Improvements
1. Improve tokenomics documentation accessibility (Mentioned by jin)
2. Create event calendar (Mentioned by jin)
3. Enrich communication content about V2/studio/marketplace (Mentioned by Zolo)
4. Update plugin documentation (Mentioned by 🧧ThanosDaSith24🧧)
5. Create guide for implementing ElizaOS as a function in Telegram bots (Mentioned by clever.sol)
6. Improve Twitter operations for important announcements (Mentioned by Zolo)
7. Clean up docs and upgrade jintern to v2 (Mentioned by jin)
8. Provide clarity on implementation team and progress tracking (Mentioned by yikesawjeez)
9. Create guide for setting up an AI agent to run social media accounts (Mentioned by eros)
10. Publish token economics details (Mentioned by chacha)

### Feature Requests
1. Implement token utility mechanisms (Mentioned by Alsara2k)
2. Build contributor analytics platform (Mentioned by Alsara2k)
3. Develop status/reputation/wearables system (Mentioned by jin)
4. Add reply approval in Discord client (Mentioned by Abderahman)
5. Implement chain of actions execution (Mentioned by Sabochee)
6. Create a system for partners to help identify posts worth reposting from the main account (Mentioned by Patt)
7. Implement the Negation Game governance system (Mentioned by yikesawjeez)
8. Use @ai16znews account as testing ground for automated newsletter posts (Mentioned by hubert)
9. Use ai16z tokens to pay for API and compute on agents (Mentioned by Alsara2k)
10. Release V2 officially (Mentioned by chacha)
11. Restore Digenai (Mentioned by chacha)
12. Develop a dashboard to organize DAO resources and make them more accessible (Mentioned by jin)