# elizaOS Discord - 2025-04-06

## Overall Discussion Highlights

### Project Status & Development
- **ElizaOS v2 Development**: The team is actively working on v2, with release expected soon. Several users are asking about migration paths to avoid duplicate work.
- **Spartan Evolution**: Odilitime has taken over as interim project manager after Rhota's departure and is working on preparing communications about "Spartan evolution" and its new Twitter account (@SpartanVersus).
- **Launchpad Launch**: Scheduled for April 14th according to mentions in the partners channel.
- **Rebranding Clarification**: yikesawjeez explained that AI16z had to rebrand to ElizaOS because a16z needs to protect its trademark, with ticker changes planned.

### Technical Discussions
- **Plugin Development**: Several users are working on plugins, including a Zilliqa plugin PR that's been pending review for weeks.
- **LLM Integration**: Free Llama 4 endpoints were announced, and users discussed OpenRouter rate limit changes.
- **Local Deployment Issues**: Multiple users reported problems with local ElizaOS deployment, including CLI errors and UI connection issues.
- **Twitter Posting System**: Kren proposed an enhanced Twitter posting system using multiple data sources with reinforcement learning to optimize post performance based on engagement metrics.
- **DAO Information Pipeline**: Jin mentioned working on a pipeline process for updates that would function as a "firehose" of information that could be plugged into agents.

### Community Concerns
- **Token Performance**: Significant discussion about AI16z/ElizaOS token price decline (from $2.4 to $0.1 over 4 months).
- **Communication Gaps**: Community members expressed desire for more regular updates rather than infrequent large releases.
- **Project Value**: Some users expressed concerns about the project's declining value.

## Key Questions & Answers

**Q: Is the request for verification of partners role in a support ticket channel legitimate?**  
A: Yes, it's legitimate. (answered by Kenk)

**Q: Will degenai holders get the same incentives as ai16z holders?**  
A: Right now holder perks are mostly discord-based, so if you hold 1M degen you should have partner status in the discord. (answered by Odilitime)

**Q: When is the launchpad launching?**  
A: April 14th (mentioned by HoneyBadger)

**Q: Is ElizaOS still an AI16z effort or totally separate?**  
A: yikesawjeez explained that AI16z had to rebrand/name change because a16z has to protect trademark, and the new name for most things is Eliza/ElizaOS

**Q: Is Shaw seriously ill?**  
A: Food poisoning (answered by HoneyBadger)

**Q: What is key function of ai16z compared with other tools such as nyfi, langgraph, n8n?**  
A: Ai16z will soon be the "best" open source one with v2, just another week (answered by DannyNOR NoFapArc)

**Q: Has anyone here tried building a Facebook client or something similar, like how we have a Twitter client?**  
A: You can see all clients here -> https://eliza.how/packages, there isn't a Facebook one - maybe their api doesn't allow for it, but there are heaps of other interfaces you can use (answered by Kenk)

## Community Help & Collaboration

1. **ElizaOS Client Packages**
   - Helper: Kenk
   - Helpee: Nazim Leeman
   - Context: User asking about building a Facebook client for Eliza OS
   - Resolution: Kenk provided a link to available client packages and explained Facebook integration might not be possible due to API limitations

2. **UI Connection Issues**
   - Helper: tatakae
   - Helpee: tolu_43743
   - Context: User experiencing UI issues with ElizaOS project toggling between connecting and disconnected states
   - Resolution: tatakae asked for logs to help diagnose the issue

3. **Twitter Functionality Troubleshooting**
   - Helper: nibbles0737
   - Helpee: tolu_43743
   - Context: User having trouble with Twitter posting functionality
   - Resolution: nibbles0737 asked about which version of ElizaOS they were using to better understand the issue

4. **DAO Participation Encouragement**
   - Helper: vincentpaul
   - Helpee: Multiple community members
   - Context: Encouraging more active participation in the DAO
   - Resolution: Suggested members introduce themselves in the DAO-org channel to contribute rather than just criticize

5. **Communication Pipeline**
   - Helper: jin
   - Helpee: Community
   - Context: Lack of regular updates and communication
   - Resolution: Created a pipeline process for updates that could function as a "firehose" of information

## Action Items

### Technical
- Review and merge Zilliqa plugin PR at https://github.com/elizaos-plugins/plugin-zilliqa/pull/1 (mentioned by mtbc)
- Fix ElizaOS CLI error with uuid dependency when creating new projects (mentioned by tolu_43743)
- Resolve local ElizaOS agent UI connection issues (mentioned by tolu_43743)
- Fix Twitter posting functionality in ElizaOS (mentioned by tolu_43743)
- Resolve Ollama configuration issues with local models (mentioned by FlipWhale)
- Investigate Pinecone index retrieval issues (mentioned by tatakae)
- Fix error when adding custom LLM inference API (mentioned by pursue)
- Implement the pipeline/firehose system for community updates (mentioned by jin)
- Development of wallet-to-social connection technology (mentioned by Odilitime)
- Prepare Spartan v2 for Twitter (mentioned by Odilitime)
- Address questions about Spartan's status (mentioned by DannyNOR NoFapArc)
- Ramp up marketing for the launchpad and v2 (mentioned by DannyNOR NoFapArc)

### Documentation
- Complete developer experience survey to improve ElizaOS framework (mentioned by Kenk)
- Communication about Spartan evolution (mentioned by Odilitime)
- Create a letter to partners similar to Jeff Bezos' shareholder letter (mentioned by 𝔭𝔩𝔞𝔱𝔞 𝔑𝔬 𝔉𝔞𝔭 𝔞𝔯𝔠)
- Highlight AI16z tokenomics more clearly in marketing materials (mentioned by HoneyBadger)

### Feature
- Develop Google Calendar integration for ElizaOS (mentioned by tolu_43743)
- Create v2 plugin-mongodb for ElizaOS (mentioned by Vladimir)
- Facebook client integration (mentioned by Nazim Leeman)
- Twitter posting system with multiple data source inputs (mentioned by Kren)
- Implement randomized flow selection for Twitter posts (mentioned by Kren)
- Reinforcement learning for Twitter post optimization (mentioned by Kren)
- Integrate the updates firehose into agents that people can engage with for updates (mentioned by jin)