# elizaOS Discord - 2025-08-07

## Overall Discussion Highlights

### Development & Technical Updates
- **ElizaOS v2 & v3 Progress**: The core team is finalizing v2 and planning for v3, with significant architecture discussions around message bus and swarm functionality. The team decided that swarm architecture should be optional rather than default for v3, as single agent implementations are simpler and faster.
- **ElizaOS Cloud Platform**: Development continues with sam-developer reporting progress on authentication, security, and API key management. JWT token issues have been fixed and API key page creation flow improved.
- **Plugin Development**: Several plugins are being actively developed:
  - A new Wolfram plugin was created by cjft in approximately 2 hours
  - The Telegram plugin received updates with PR #11 from an intern
  - Discussion about adapting the "Ruler" framework (an LLM-as-judge system) for TypeScript to improve plugin testing
- **Migration Issues**: A user named Christopher encountered compatibility problems when upgrading from ElizaOS v0.1.9 to v1.3.2, with errors in the Postgres adapter. The team clarified that significant architecture changes occurred between versions and directed users to use the newer eliza-nextjs-starter repository instead of the archived eliza-starter project.
- **GPT-5 Release**: The team discussed the capabilities and limitations of the newly released GPT-5, with OpenRouter's GPT-5 release also mentioned.

### Community & Market Dynamics
- **Token Market Discussion**: Community members questioned wallet activities and potential market manipulation affecting ai16z token. A team member (jasyn_bjorn) clarified they don't have a market-making agreement with Wintermute, despite community suspicions.
- **Competitor Relations**: A situation was discussed where another project called Poink (a side project of the OpenServ team) was spreading what was described as FUD about ElizaOS. Investigation revealed this appeared to be a competitive tactic rather than legitimate technical critique.
- **AI Trends**: Community members expressed optimism about AI technology trends returning, similar to Q3 last year, with agents becoming relevant again.
- **Clanktank Agent Review System**: The system is operational but needs refinement, with jin sharing the dashboard and noting that the AI reviews might be too harsh.

### Platform Features & User Experience
- **AI Assistant Functionality**: Users praised Eliza's AI assistant capabilities but noted it lacks information about OpenAI token requirements for building effective agents.
- **Social Media Access**: Several members mentioned anticipation for regaining access to their X/Twitter account, which appears to be currently unavailable but considered important for marketing and community growth.

## Key Questions & Answers

**Q: Does the latest version of ElizaOS support Postgres?**  
A: Yes, you just need to provide POSTGRES_URL in the .env file (answered by 0xbbjoker)

**Q: Can I update Eliza to the latest version in the eliza-starter project?**  
A: No, that repo is archived and not supported anymore. Use eliza-nextjs-starter instead (answered by 0xbbjoker)

**Q: How should we approach the message bus architecture for v3?**  
A: It should be optional rather than default, with single agent as the default for simplicity and speed (answered by cjft)

**Q: Do you have a market making agreement with Wintermute?**  
A: "We do not & have not had a MM agreement with WM, we can't restrict them from trading" (answered by jasyn_bjorn)

**Q: What's the status of ElizaOS v2?**  
A: Basically done, with partner plugins like Wolfram being developed quickly (answered by cjft)

**Q: Can Eliza run on t3.micros for hosting?**  
A: Not currently, only on smalls, but yikesawjeez mentioned someone got v1 running on t4g.small (free tier) (answered by yikesawjeez)

**Q: What is the relationship between Poink and OpenServ?**  
A: Poink is a side project of the OpenServ team, confirmed by Kenk after speaking with the Poink founder who is also an admin in the OpenServ Discord.

## Community Help & Collaboration

1. **Migration Assistance**:
   - Helper: 0xbbjoker | Helpee: Christopher
   - Context: Error with Postgres adapter when upgrading ElizaOS from v0.1.9 to v1.3.2
   - Resolution: Directed to use the newer eliza-nextjs-starter repository and provided a PR with configuration instructions

2. **Wallet Activity Analysis**:
   - Helper: pangolink | Helpee: Dai00
   - Context: Identifying wallet activities and explaining market making
   - Resolution: Explained that one wallet has interacted with Wintermute hot wallets and likely relates to market making activity

3. **FUD Investigation**:
   - Helper: Kenk | Helpee: Channel members
   - Context: Understanding the source and validity of FUD being spread about ElizaOS
   - Resolution: Kenk investigated and provided clarity that it was a competitive tactic from OpenServ with no technical merit

4. **Plugin Development Support**:
   - Helper: cjft | Helpee: Team
   - Context: Wolfram plugin development
   - Resolution: Created functional plugin in about 2 hours

5. **Cloud Platform Improvements**:
   - Helper: sam-developer | Helpee: Team
   - Context: Eliza cloud platform authentication and security issues
   - Resolution: Fixed JWT token issues, API key page creation flow, and pushed PR to dev branch

## Action Items

### Technical
- Fix pino logger changes that broke entire monorepo (Mentioned by cjft)
- Implement validator feature for tools to solve tool bloat (similar to GPT-5's approach) (Mentioned by cjft)
- Adapt Ruler framework to TypeScript for plugin testing (Mentioned by shaw)
- Simplify message bus/swarm architecture to make it optional (Mentioned by cjft)
- Develop interactive modes for CLI (Mentioned by cjft)
- Resolve remaining issues on the generate page for Eliza cloud (Mentioned by sam-developer)
- Use eliza-nextjs-starter repository instead of archived eliza-starter for ElizaOS v1.3.2+ (Mentioned by 0xbbjoker)
- Leave default agentId and worldId from .env_example when setting up eliza-nextjs-starter (Mentioned by 0xbbjoker)
- Run "bun run dev:with-agent" to start the project (Mentioned by 0xbbjoker)
- Regain access to X/Twitter account (Mentioned by Multiple users including phetrusarthur✈ and 3on_)
- Provide information about OpenAI token requirements for building agents in Quick start options (Mentioned by 3on_)

### Feature
- Support for running Eliza on smaller instances (t3.micros) (Mentioned by cjft)
- Implement workflows in v3 with Orchestrator for agent groups (Mentioned by cjft)
- Develop desktop/mobile apps for Eliza (Mentioned by cjft)
- Improve emoji design for Eliza - focus on facial expressions rather than full-body emojis (Mentioned by satsbased)
- Consider community engagement strategies in response to competitor FUD (Mentioned by Rick)

### Documentation
- Update documentation with changes from sam-developer (Mentioned by Borko)
- Update documentation to reflect architecture changes between ElizaOS v0.1.x and v1.3.x (Mentioned by 0xbbjoker)