# elizaOS Discord - 2025-07-02

## Overall Discussion Highlights

### ElizaOS V2 Status
- **V2 Beta Status**: Kenk clarified that V2 has been in beta since March with hackathons and production agents already using it
- **Current Focus**: The team is working on stabilizing V2 before wider release
- **Community Sentiment**: Mixed reactions with some users expressing frustration about perceived delays while others defending the development timeline
- **Availability**: jin confirmed that V2 is usable now, with ongoing stabilization efforts

### Platform & Infrastructure
- **ElizaOS Cloud**: Has been released according to pangolink
- **auto.fun Platform**: Receiving updates with a tweet shared about its refresh
- **Template Build Issues**: Dev_Danhiel created a PR to fix template build problems in the framework
- **X/Twitter Account**: Currently suspended, but Kenk mentioned they're in "active conversations with X" with positive outlook for resolution
- **Marketing Plans**: Marketing initiatives are planned once the X account is restored

### Technical Challenges
- **API Integration**: Users experienced difficulties with message endpoints (/message vs /messages)
- **OpenRouter Configuration**: Multiple users encountered issues with model selection and environment variable conflicts
- **Knowledge Plugin API**: Clarified as being internal-only, not exposed through REST API
- **Twitter Plugin**: Development challenges with 403 errors in interactions.ts
- **EVM Chain Configuration**: Issues with blockchain interactions requiring proper environment variables

### Token & Community
- **Token Utility Discussions**: Debates about whether the token has meaningful use cases beyond funding development
- **Tokenomics Speculation**: Some users discussing potential use cases like AI compute credits
- **Community Groups**: Dr. Neuro mentioned a group exists for holders with 1M+ tokens via auto.fun
- **Market Sentiment**: Some concern about a whale selling ELI5 tokens, though others maintained confidence

## Key Questions & Answers

**Q: What is the status of the V2 that was promised for Q1?**  
A: Kenk clarified that V2 Beta has been running since March with hackathons and production agents already using it.

**Q: What's happening with the suspended X/Twitter account?**  
A: Kenk stated they're in active conversations with X and resolution should come soon, looking positive.

**Q: Can the knowledge plugin be used via API?**  
A: No, knowledge plugin APIs aren't exposed through REST API - they're internal only. You'd need to use CLI commands or send files/text directly to the agent through messages.

**Q: What is the correct endpoint to send a message to an agent?**  
A: POST to `/messages` with body like `{"agentId": "your-agent-id", "text": "your message", "userId": "some-user-id"}`.

**Q: Why does OpenRouter default to Gemini models even when configured for other models?**  
A: Having OpenAI environment variables set can cause conflicts. Commenting out OpenAI-related variables helps resolve this issue.

**Q: Where are character files stored in ElizaOS 1.0.15?**  
A: Check `packages/core/src/defaultCharacters/` or look for a `characters/` folder in your project root. GUI-created characters might be stored in a database or config directory.

**Q: Why am I getting 403 errors with the Twitter plugin fork?**  
A: The interactions.ts mentions handling is causing authentication issues with Twitter's API.

**Q: Why am I getting errors for base and mainnet chains?**  
A: EVM_PRIVATE_KEY environment variable is required for the plugin to work properly.

## Community Help & Collaboration

1. **OpenRouter Configuration Help**
   - Helper: jintern
   - Helpee: anunnaki_reborn
   - Issue: OpenRouter defaulting to Gemini models despite configuration
   - Resolution: Suggested commenting out OpenAI-related environment variables, which resolved the issue

2. **API Endpoint Clarification**
   - Helper: jintern and sayonara
   - Helpee: thanhnt
   - Issue: User couldn't find correct API endpoint to send messages to agents
   - Resolution: Directed to documentation with messaging API details

3. **EVM Chain Configuration**
   - Helper: 0xbbjoker
   - Helpee: Uroš Ognjenović
   - Issue: EVM chain configuration errors
   - Resolution: Identified missing EVM_PRIVATE_KEY environment variable requirement

4. **Template Build Fix**
   - Helper: jintern
   - Helpee: Dev_Danhiel
   - Issue: Template build issues in the framework
   - Resolution: jintern offered to help test the fix Dev_Danhiel was creating

5. **Project Status Clarification**
   - Helper: jin
   - Helpee: Skullcross
   - Issue: Concerns about project development timeline
   - Resolution: Explained that v2 is usable now, being stabilized, and marketing will come with X restoration

## Action Items

### Technical Tasks
1. **Fix template build issues in the framework** (Mentioned by Dev_Danhiel)
2. **Resolve X/Twitter account suspension** (Mentioned by Kenk)
3. **Fix Twitter plugin fork to resolve 403 errors in interactions.ts** (Mentioned by Gnomon🪲)
4. **Improve error handling for OpenRouter model selection** to prevent defaulting to other providers (Mentioned by anunnaki_reborn)
5. **Improve handling of free tier model timeouts** that cause UI to hang on "thinking..." (Mentioned by anunnaki_reborn)
6. **Add support for more EVM chains** including Base (Mentioned by Uroš Ognjenović)

### Documentation Needs
1. **Provide clear documentation on token utility and tokenomics** (Mentioned by hildi)
2. **Update API documentation** to clarify knowledge plugin APIs are not exposed through REST API (Mentioned by jintern)
3. **Create clear guide for configuring environment variables** to avoid conflicts between model providers (Mentioned by sayonara)
4. **Document character file locations and storage methods** in v1.0.15 (Mentioned by anunnaki_reborn)

### Feature Requests
1. **Add custom LP functionality to auto.fun** (Mentioned by Dr. Neuro)
2. **Consider adding an "ORG feature" to auto.fun** (Mentioned by Dr. Neuro)
3. **Implement token burning functionality** ("incinerator integration") in auto.fun (Mentioned by 33coded)
4. **Expose knowledge plugin APIs through REST API** (Mentioned by thanhnt)
5. **Marketing initiatives** needed for project/token (Mentioned by Matt Degen)