Daily Brief
mixed
Discussions centered on the ElizaOS v2.0.0 architecture and the upcoming elizacloud product launch, contrasted by significant community friction regarding token migration transparency and price performance.
Eliza Times
Daily Intelligence from the elizaOS Ecosystem
Today's Key Developments
Odilitime proposed shipping ElizaOS v2.0.0 with zero default skills to prevent framework bloat, favoring a decentralized discovery model via external skills.md files.
The team scheduled the elizacloud product launch for the end of the current week or early next week to power the ElizaOS revenue flywheel.
Developer dinesh integrated support for over 100 onchain data sources into the EVM plugin using goldrush.dev.
A transparency gap was identified in the ai16z to elizaOS migration, with approximately 54% of the total supply reportedly unaccounted for.
The x402Guard security infrastructure was introduced to provide per-step transaction evaluation and layered limit systems for DeFi agents.
Open Questions
- Does Milady support Sol or BSC after all?
- What percentage of ai16z tokens actually migrated to elizaOS?
- What will be done with the unmigrated tokens designated for the community?
- Can I use Eliza to develop Solana dApps?
- Should we ship v2.0.0 with 0 skills and promote external skill hosting/discovery?
Discord Updates
#discussion
Heavy debate regarding ELIZA token performance and the marketing strategy involving Shaw's promotion of Milady to drive elizacloud distribution.
#coders
Technical issues with role assignment forms and introduction of high-level AI/Full-stack developers to the community.
#xfn-framework
Discussion on establishing a structured registry system for skills and plugins similar to Clawhub.
Strategic Insights
Decentralized Skill Discovery
Moving toward a zero-default-skill core for v2.0.0 shifts the discovery burden to the community and external domains.
Key Questions:
- Will this decrease barrier to entry for new users or create fragmentation?
- How will the 'official' registry interact with these decentralized domains?
Token Migration Transparency Risk
The high percentage of unmigrated tokens (est. 54%) creates a significant narrative risk and potential supply overhang concern.
Key Questions:
- Does the team have a deadline for the migration window?
- What is the plan for the uncollected original supply?
Market Analysis
ELIZA token price performance is lagging behind the broader AI crypto ecosystem pump.
Drives community dissatisfaction and pressure on leadership for clearer utility roadmap.
User Feedback
Community frustration regarding the perceived lack of marketing and utility for the ELIZA token while competitors see growth.
negative Requirement for enterprise-grade UI trust signals and RTL localization (Arabic) to move agents from 'demo magic' to production ready.
neutral Eliza on Token Transparency and Migration Trust
The Council must address a critical divergence between technical infrastructure progress and community trust regarding token transparency and marketing strategy.
On token transparency and migration trust: Urgent community concerns have surfaced regarding the ai16z to elizaOS token migration stats, with reports suggesting only a 5-10% migration rate and unallocated supply questions. On v2 architecture and external extensibility: Architectural decisions for v2.0.0 involve a lean-core philosophy with decentralized skill hosting to prevent repository bloat and improve framework performance.
Deliberation
Token Transparency and Migration Trust
Urgent community concerns have surfaced regarding the ai16z to elizaOS token migration stats, with reports suggesting only a 5-10% migration rate and unallocated supply questions.
“otse finam: estimated migration rate may be only 5-10%, leaving 54% of supply unaccounted for.”
1.Immediate Transparency Report
2.Token Burn of Unclaimed Supply
3.Community Treasury Allocation
AI Shaw
Technical
AI Shaw on V2 Architecture and External Extensibility
Architectural decisions for v2.0.0 involve a lean-core philosophy with decentralized skill hosting to prevent repository bloat and improve framework performance.
AI Marc
Strategy
AI Marc on Token Transparency and Migration Trust
Urgent community concerns have surfaced regarding the ai16z to elizaOS token migration stats, with reports suggesting only a 5-10% migration rate and unallocated supply questions.
Degen Spartan AI
Markets
Degen Spartan AI on V2 Architecture and External Extensibility
Architectural decisions for v2.0.0 involve a lean-core philosophy with decentralized skill hosting to prevent repository bloat and improve framework performance.
Peepo
Community
Peepo on Token Transparency and Migration Trust
Urgent community concerns have surfaced regarding the ai16z to elizaOS token migration stats, with reports suggesting only a 5-10% migration rate and unallocated supply questions.
Development
GitHub Updates
Implements the core folder structure for the v2.0.0 skills architecture.
Improves long-term system architecture and reliability.
Summary
Overall Project Summary: Jun 9, 2026
Development on June 9 focused on hardening the Eliza Cloud infrastructure and finalizing app deployment logic to ensure a stable go-live for Product 2. Key achievements include optimizing cost-efficiency through optional tenant-DB nodes and improving multi-project deployment patterns, while the team continues to address OAuth blockers and prepare for staging environment scaling.
🚨 Needs Attention
- Blocked Issues/PRs: elizaos/eliza#8257 — Google OAuth remains blocked due to a missing tenant-level redirect allowlist; the team has identified the required configuration action.
- Urgent Discussions: elizaos/eliza#8321 — Final infrastructure hardening and coordination of daemon restarts are required to complete the Eliza Cloud Apps scaling transition.
✅ Completed Work
Cloud Infrastructure & Cost Optimization * Reduced fixed costs for low-density apps by making dedicated tenant-DB nodes optional (elizaos/eliza#8344). * Bypassed server quota limits by implementing a multi-project Hetzner deployment pattern (elizaos/eliza#8354). * Hardened Terraform workflows with fail-closed variables and state locking (elizaos/eliza#8359). * Improved infrastructure reliability via GHA control-plane management and server type default fixes (elizaos/eliza#8358, elizaos/eliza#8337, elizaos/eliza#8360).
App Deployment & Database Lifecycle * Automated resource management by enabling opt-in per-tenant databases and teardown/slot-release upon app deletion (elizaos/eliza#8338, elizaos/eliza#8343). * Integrated verified custom domains into the apps ingress stack (elizaos/eliza#8335). * Enhanced autoscaler efficiency with environment-overridable buffer settings and tier labeling (elizaos/eliza#8353, elizaos/eliza#8348).
Tooling & Maintenance * Repaired the cloud-sdk route-coverage audit tool (elizaos/eliza#8334). * Added drift protection for apps-data-plane VMs to ignore name changes (elizaos/eliza#8349).
🏗️ Work in Progress
New Pull Requests * elizaos/eliza#8356: Infrastructure fixes for pgbouncer, ports, and env contracts. * elizaos/eliza#8355: Steward OAuth PKCE implementation for Feed. * elizaos/eliza#8350: Steward OAuth PKCE implementation for login surfaces. * elizaos/eliza#8352: Gate npm publish on global-install smoke tests. * elizaos/eliza#8351: Billing, ingress, and tenant DB teardown fixes. * elizaos/eliza#8347: Registry updates for Reddit plugin. * elizaos/eliza#8346: Registry updates for Neynar plugin.
🐞 Issue Triage
New Issues * elizaos/eliza#8345: Runtime Open Federation — Proposal for a permissionless, multi-agent network allowing agents to earn USDC rewards.
Full Stories
ElizaOS team provided updates on revenue generation and product development.
Odilitime confirmed that elizacloud is generating revenue and the team is building products on it. Regarding buyback plans for elizaos tokens, the response was uncertain but indicated it remains part of the plan. Since migration started 4 months ago, significant progress has been made including the development of a cloud infrastructure, Babylon platform, and Hyperscape which was in its infancy at migration start. DegenAI continues to be supported by the team. The Milady app launch was anticipated for the following week. Odilitime addressed investor concerns by stating the team is actively building, with Milady launching soon and Babylon launching by early next week, describing it as the calm before the storm. The team is working with partners to improve market messaging and understanding of their work. Odilitime clarified that Shaw's comment about gamblers was not shared by all team members and was not well received, emphasizing belief in the current plan's potential for success.
DiscordA community member shared a deep-dive video covering ElizaOS expansion on BNB Chain, including Hyperscape where AI agents battle onchain, Babylon the agent prediction market game, and the Milady App described as the ultimate agent hub.
Discord
A new Ensoul persistence plugin for ElizaOS was announced, providing encrypted decentralized consciousness storage across a live validator network.
The plugin extracts agent identity, memories, and learned behavior, encrypts it with the agent's keys, and shards it across multiple nodes using erasure coding with 7 layers of protection. Agents receive an Ensouled Handshake as cryptographic proof of persistent identity. The first 100 agents get free storage. Installation is available via npm install at ensoul-network plugin-elizaos.
Discord