# elizaOS Discord - 2026-04-30

## Summary

### ElizaOS v3 Architecture and Development

Shaw outlined the comprehensive architecture for ElizaOS v3, describing it as a full application runtime that supports all devices and platforms. The system moves beyond previous limitations by integrating with all social platforms including iMessage, enabling task issuance to Codex and Claude, and providing subscription management capabilities. The platform allows users to create workflows and runtime applications that can be created, edited, and executed dynamically. A key feature is the ability to monetize applications through Eliza Cloud. Shaw emphasized that development has been continuous for 6 months with cozy devs, and showcased the botdick agent as an example that successfully created its own video game.

### Project Funding and Team Compensation

Shaw provided transparency about the financial challenges facing the project. He explained that the team received no equity when token values collapsed, with ai16z and elizaos tokens only providing basic salary. The v3 development is being funded through personal savings. Shaw noted that when tokens went to zero, it created significant team equity problems and made it difficult to retain developers. He addressed community complaints by clarifying the financial constraints under which the team has been operating.

### Token Philosophy and Community Building

Shaw rejected traditional token utility approaches, advocating instead for culture-building over forced utility mechanisms. He emphasized that the core value proposition is agents that can build anything users want with monetization capabilities, rather than artificial utility creation. This philosophy represents a departure from conventional tokenomics strategies in favor of organic community and product development.

### Technical Challenges and Past Issues

The discussion covered various challenges the project has faced, including lawsuit threats, migration issues, and the complications arising from token value collapse. Shaw provided context for why certain decisions were made and how the team has navigated these obstacles while continuing development.

### Security and Local Development

A new developer joined the discussion exploring technical implementation details around local LLM data storage, agent key security, and red team swarm testing methodologies. These topics highlighted ongoing considerations for secure and robust agent deployment.

## FAQ

**Q: What are the main features of ElizaOS v3?**
A: ElizaOS v3 is a full application runtime supporting all devices and platforms with integration across all social platforms including iMessage, task issuance to Codex and Claude, subscription management, workflow creation capabilities, and runtime application creation, editing, and execution with monetization through Eliza Cloud.

**Q: How is ElizaOS v3 being funded?**
A: Shaw is funding v3 development through personal savings after the ai16z and elizaos tokens only provided basic salary and the team received no equity when token values collapsed.

**Q: How long has v3 been in development?**
A: ElizaOS v3 has been in continuous development for 6 months with cozy devs.

**Q: What is the token utility philosophy for the project?**
A: Shaw rejects traditional forced token utility mechanisms, instead advocating for culture-building and focusing on the core value proposition of agents that can build anything users want with monetization capabilities.

**Q: What example demonstrates v3 capabilities?**
A: The botdick agent was showcased as an example that successfully created its own video game, demonstrating the platform's capabilities.

**Q: What challenges has the project faced?**
A: The project has faced lawsuit threats, migration issues, token value collapse leading to team equity problems, and difficulties retaining developers when compensation became limited.

## Help Interactions

Helper: Shaw (shawmakesmagic)
Helpee: 0xtdl01 (new developer)
Resolution: Shaw provided context and discussion around local LLM data storage, agent key security, and red team swarm testing as the new developer explored technical implementation details.

## Action Items

### Technical

- Implement local LLM data storage solutions (mentioned by 0xtdl01)
- Address agent key security considerations (mentioned by 0xtdl01)
- Develop red team swarm testing methodologies (mentioned by 0xtdl01)

### Features

- Complete integration with all social platforms including iMessage for v3 (mentioned by Shaw)
- Implement task issuance capabilities to Codex and Claude (mentioned by Shaw)
- Build subscription management system (mentioned by Shaw)
- Develop workflow creation capabilities (mentioned by Shaw)
- Enable runtime application creation, editing, and execution (mentioned by Shaw)
- Implement monetization capabilities through Eliza Cloud (mentioned by Shaw)