# elizaOS Discord - 2025-01-29

## Overall Discussion Highlights

### Project Management & Governance
- **Treasury Management Crisis**: A significant controversy emerged regarding the DAO treasury selling tokens from partner projects. Shaw explained this was part of emergency measures to protect their token and fund development, clarifying they have a $3M annual development budget. The community ultimately rejected the proposal to sell partner tokens, with Shaw canceling the proposal.
- **Leadership Updates**: rhota has taken a more active leadership role in DegenAI development, with a full-time team including neo, saaaanti, and odilitime.
- **DUNA Legal Structure**: Discussions about implementing a Wyoming-based Decentralized Unincorporated Nonprofit Association (DUNA) legal structure for the DAO, which could solve many tokenomics challenges.
- **Governance Implementation**: The team is working on implementing a DAO voting mechanism using Realms.today, which requires token deposits for governance power.

### Technical Development
- **ElizaOS Framework**: The project has rebranded to ElizaOS (framework) while maintaining ai16z as the token ticker, causing some marketing confusion.
- **Launchpad Development**: Multiple users inquired about the upcoming launchpad, which is nearing completion and will be a key revenue generator.
- **DegenAI Focus**: Autonomous trading capabilities are the #1 priority for DegenAI, with plans to expand functionality to include CEX support, contract trading, and better token filtering.
- **Plugin Ecosystem**: Discussions about integrating various ElizaOS plugins into agents and expanding functionality across platforms.
- **New Integration**: ElizaOS now has an official Twitter account and a new plugin integration with Lit Protocol for agent wallets with on-chain controls.

### Technical Challenges
- **Model Provider Issues**: Users reported Deepseek being down for several days due to high demand or possible DDOS attacks.
- **Database Configurations**: Discussions about connecting ElizaOS with databases (particularly Postgres), with users sharing workarounds for SQLite, Redis, and MongoDB.
- **Twitter Integration Problems**: Several users mentioned issues with Twitter hiding agent replies and authentication challenges.
- **Installation Difficulties**: Windows users experienced significant installation problems, with some switching to Ubuntu to resolve these issues.

### Tokenomics & Funding
- **Tribute System**: Debate over the proper handling of partner token tributes (LP vs. selling), with suggestions to formalize the system with clear terms, possibly reframing as "partner fees" with programmatic contracts.
- **Tokenomics Paper**: Jin shared notes about mechanisms including tributes, buybacks, retro funding, and marketplace tokenomics. The paper is reportedly complete and focuses on the launchpad.
- **Contributor Incentives**: Plans to implement retroactive airdrops of treasury tokens to GitHub contributors based on their contributions.

## Key Questions & Answers

**Q: Why is the DAO treasury address selling off donated assets?**  
A: Shaw explained they needed to take emergency measures to protect their token and fund development costs of $3M per year. The team filtered out tokens based on specific criteria (less than 5% holdings, under $20K value, or unknown projects).

**Q: When will the launchpad be launched? Is it after v2 or before?**  
A: Jin indicated it's close but didn't provide a hard date. Shaw mentioned it's almost done and will be a key focus of the tokenomics paper.

**Q: Is it possible for AI agents to be placed "behind" NFTs in the Json files for the metadata?**  
A: Kirsten explained that while you can't put a whole agent behind an NFT (as metadata is public), you can gate access to agents via NFT ownership verification.

**Q: How can I fix the "Vector dimension mismatch" error?**  
A: Set USE_OPENAI_EMBEDDING=TRUE in your .env file.

**Q: How do I prevent my Twitter bot from getting banned?**  
A: Use an older account, get a subscription, mark it as automated in your bio, and reduce posting frequency.

**Q: How do I fix the DTS build error?**  
A: Use the develop branch which has the fix, or switch to the eliza repo instead of eliza-starter. Then run pnpm clean, pnpm install -r, pnpm build.

**Q: What EC2 instance type is suitable for running Eliza?**  
A: Use t3.medium with 2 CPUs, 4GB RAM, and ensure swap is enabled. Estimated operational cost is $20/month.

**Q: Why did Shaw just sell off all his DegenAI?**  
A: Shaw sold his personal allocation, but the team is still committed to the project. Some clarified that tokens weren't sold but placed in liquidity pool.

**Q: What is the current definition and plan for DegenAI from the team's perspective?**  
A: rhota has taken leadership and is providing more regular updates. The team is focusing on autonomous trading capabilities as the #1 priority.

**Q: What can we expect from the upcoming tokenomics plan?**  
A: More info about the upcoming marketplace/launchpad and detailed documentation of tokenomics mechanisms: 1. 10% Tributes + phase 2 plans, 2. DegenAI buybacks from daos.fun, 3. AI KOL / Memecoin traders, 4. Retro Funding for Contributors, 5. AI Investors + Game Show, 6. Agent Marketplace Tokenomics.

## Community Help & Collaboration

**Vector Dimension Mismatch Error**  
Helper: mike🇭🇺 | Helpee: mike🇭🇺  
Context: User was experiencing vector dimension mismatch errors with database embeddings.  
Resolution: Discovered setting USE_OPENAI_EMBEDDING=TRUE in the .env file resolves the issue.

**Agent Truthfulness Configuration**  
Helper: Mr. Stark | Helpee: Mad  
Context: Agent making up answers when it doesn't know something.  
Resolution: Suggested adding explicit instructions in character lore like "Like George Washington I never tell a lie and if I don't know something I will just say I do not know."

**EC2 Deployment Guidance**  
Helper: C-Money-Dev | Helpee: A-Aron  
Context: User needed advice on suitable EC2 instance for running Eliza.  
Resolution: Recommended t3.medium with swap enabled, estimated $20/month operational cost, and provided detailed setup instructions.

**NFT-Gated Agent Implementation**  
Helper: Kirsten | Helpee: +303FPV  
Context: User wanted to implement NFT-gated AI agents.  
Resolution: Explained that while you can't put agents in NFT metadata (as it's public), you can gate access to agents via NFT ownership verification.

**Organizational Structure Visualization**  
Helper: DorianD | Helpee: Community  
Context: Confusion about project structure and roles.  
Resolution: Created and shared a Google Drawing organizational chart that partners could contribute to for better coordination.

**Treasury Token Sales Explanation**  
Helper: Shaw | Helpee: Community  
Context: Explanation of DAO treasury token sales that caused community concern.  
Resolution: Clarified they filtered out tokens based on specific criteria (less than 5% holdings, under $20K value, or unknown projects) and ultimately canceled the proposal based on community feedback.

## Action Items

### Technical
- Fix Deepseek and Gemini model provider integration (Mr. Stark)
- Resolve vector dimension mismatch between different embedding models (mike🇭🇺)
- Fix image processing in Twitter client (blockbyt)
- Implement proper error handling for Twitter login attempts (Pedro)
- Fix DTS build errors in the main branch (engineer)
- Optimize agent startup time by removing unused imports (Kren)
- Fix Discord client image handling (mike🇭🇺)
- Fix Telegram client API errors (Bizzo)
- Fix module dependency issues in elizaOS Windows installation (Shelia)
- Implement autonomous trading as the #1 priority for DegenAI (rhota)
- Develop CEX support and contract trading (tigerguo.)
- Create chain-scanning strategy for token filtering (tigerguo.)
- Integrate with trenching tools like Gitlarp (kalshnikov)
- Implement post-trade reviews for DegenAI (kalshnikov)
- Develop trading monitor/alert bot (ricky)
- Implement a proper multisig wallet setup for treasury management (mattyryze)
- Create a website to track tributes over time including LP positions (jin)
- Implement retroactive airdrops for GitHub contributors (shaw)
- Develop a contributor leaderboard (jin)
- Implement the DUNA legal structure for the DAO (shaw)
- Fix X (Twitter) handles to clearly associate ElizaOS with the ai16z token (HoneyBadger)
- Disable thread creation in official channels to prevent scammers (Patt)

### Documentation
- Update contributing guide to recommend develop branch for plugin development (chriskim)
- Create documentation for MongoDB adapter (anyadachan)
- Document Direct client API endpoints (wacaine)
- Create guide for setting up Eliza on EC2 (A-Aron)
- Document memory management system (Psyxh)
- Create comprehensive elizaOS Windows installation guide (Shelia)
- Publish tokenomics model (tigerguo.)
- Create project roadmap (tigerguo.)
- Improve communication strategy with regular updates (DorianD)
- Create curated list of agents built with ElizaOS (uneke)
- Clarify partner requirements in accessible documentation (pajamaparty1)
- Document airdrop eligibility for token holders (pajamaparty1)
- Complete FAQ documentation with answers to remaining 32% of questions (jin)
- Create bounties for community members to help refine answers to FAQs (jin)
- Create clear documentation for the tribute/partner fee system (hamlet)
- Publish the tokenomics whitepaper (阿拉斯加的狗🔯)
- Create an organizational chart showing roles and responsibilities (DorianD)
- Review and simplify Vasily's proposal on market mechanisms (yikesawjeez)

### Features
- Implement modular plugin architecture for V2 (chriskim)
- Add ability to update character data while agent is running (Erin)
- Create chatbot-style UI component for website integration (piffie)
- Add voice messages to Telegram client (Dark Cobra)
- Implement better RAG capabilities (JimmyC15)
- Add ability to post news from database to social media (BigR)
- Develop launchpad for agent deployment (Gogo, nancy_fi1313237_96389)
- Release tokenomics paper and roadmap (nancy_fi1313237_96389)
- Create waifu NFT functionality for DegenAI (Patt)
- Create distinction between projects the DAO chooses to invest in vs those that tribute tokens (Patt)
- Implement special benefits for investment-category projects (kalshnikov)
- Consider implementing revenue sharing from pmairca & DegenAI trading profits (Patt)
- Create leaderboard for top agents by marketcap with rewards (Patt)
- Launch the ElizaOS launchpad (shaw)
- Implement a staking mechanism for governance (jin)
- Change the token ticker to align with the ElizaOS rebrand (renameless)
- Implement a Discord-based proposal and voting system (Ka_yari)
- Set up weekly Discord stage events for team updates (DorianD)
- Develop a terminal interface to show AI decision-making (pragmatiko)
- Create a basic newsletter website using JSON from the AI news aggregator (jin)