# Fact Briefing: 2026-04-29

## Overall Summary
The project is approaching a major release with Eliza v3 and Milady integration nearing completion, while concurrently managing a critical technical blocker in the dependency modernization stack. A significant utility milestone was achieved by implementing $ELIZA as the default payment method for x402 infrastructure services.

## Key Facts

- Shaw announced Eliza v3 and Milady integration are nearing completion with a release expected in the coming weeks.
- $ELIZA token has been implemented as the default payment method for elizaOS/Milady services in x402 infrastructure.
- PR #7146 is identified as a critical blocker for the project's migration to Node.js 24, TypeScript 6, and Bun 1.3.13.
- The cloud infrastructure transitioned from Vercel AI Gateway to OpenRouter, using OpenAI and Anthropic as failovers.
- Eliza Cloud has commenced operational service for business clients with direct app integration capabilities.
- CLI authentication hangs were resolved by implementing auto-clearing for stale Steward and Privy tokens.
- A documentation and security vulnerability was identified regarding a non-functional Milady Play Store link in the GitHub repository.
- Community coordination remains a priority with the formation of the 'eliza army' steering group and a Hyperscape Discord invite.

## Open Questions

- What is the specific news regarding Milady?
- Can we expect some update for $degenai this month?

## Categories

### GitHub Updates

#### New Issues/PRs
- [Pull_request #7146: PR #7146 (Dependency Blocker)](https://github.com/elizaos/eliza/pull/7146) by unknown - Status: open - Significance: Crucial transitive dependency fix required to unblock the entire modernization stack.
- [Pull_request #6530: V2.0.0 release](https://github.com/elizaos/eliza/pull/6530) by odilitime - Status: open - Significance: Massive modernization of CI/CD and release automation across multiple languages.
- [Issue #6688: Plugin Proposal: AgentID](https://github.com/elizaos/eliza/issues/6688) by haroldmalikfrimpong-ops - Status: closed - Significance: Established cryptographic identity and trust layer for agents using Ed25519.

#### Overall Focus
- The repository is currently focused on an infrastructure modernization effort targeting Bun 1.3.13 and React 19.2.5, though CI/CD regressions are present due to dependency install failures.

### Discord Updates
- **#discussion:** Focus on Eliza v3 readiness and token utility. Discussions shifted from price speculation to infrastructure-linked payments ($ELIZA in x402). (Key Participants: shawmakesmagic, odilitime, zadayos)
- **#coders:** Minimal activity; primarily focused on moderation and removing scammers. (Key Participants: odilitime, danoski)

### User Feedback
- Users expressed significant concern regarding market performance and requested VC partnerships to stabilize token price. (Sentiment: negative)
- Community members suggested increasing communication frequency and developing clearer PR and business planning materials. (Sentiment: neutral)

### Strategic Insights

#### Token Utility vs Friction
The project is pivoting toward an indirect token support model—accepting any payment and using revenue for buybacks—to avoid user friction while maintaining buy pressure.

*Implications/Questions:*
  - Will this buyback model satisfy investors concerned about direct token utility?

#### Infrastructure Blockage
High architectural technical debt in dependencies is causing a deadlock where undetected regressions may leak into the codebase due to failing CI/CD workflows.

*Implications/Questions:*
  - Is there a manual fallback for PR validation while the Bun install issue persists?

### Market Analysis
- Transition of $ELIZA to a default payment method for x402 infrastructure. (Relevance: Moves the token from purely speculative to a service-fee/commodity model.)