# Fact Briefing: 2026-05-03

## Overall Summary
ElizaOS is undergoing a massive infrastructure stabilization effort with the consolidation of the v3 architecture and essential security improvements like the new cross-platform vault. Technical focus has shifted toward resolving critical Telegram integration issues and neutralizing memory degradation in long-lived agents.

## Key Facts

- Shaw announced ElizaOS v3 as a full application runtime supporting cross-platform social integration and Eliza Cloud monetization.
- PR #7197 successfully merged the @elizaos/vault package, providing cross-platform AES-256-GCM encryption for secrets using OS keychains.
- A critical process-level segfault affecting headless Linux servers was resolved by bypassing the OS keychain when D-Bus is unavailable in PR #7230.
- Developer marianodim is building an ElizaOS spot trading agent for SOL, SUI, and five other tokens, targeting 1-2 signals per week.
- Research by sentient_dawn identified 'memory rot' in agents after three months of operation, resulting in a proposed solution using freshness gates and reconciliation passes.
- Shaw disclosed that ElizaOS v3 development is currently funded through personal savings following the collapse of team equity in previous tokens.
- Telegram integration is currently hampered by dual-polling race conditions between the core plugin and the Milady wrapper as documented in Issue #7245.
- Infrastructure modernization included upgrades to TypeScript 6, Node.js v24, and a migration of the Cloud platform to Vite and Hono Workers.

## Open Questions

- What is the standard implementation path for environment variable handling regarding voice.ts vs messages.ts in the Discord configuration?
- Why does the dev-ui.mjs reference a non-existent ./claude-code-stealth.mjs preload on fresh clones?

## Categories

### GitHub Updates

#### New Issues/PRs
- [Pull_request #7197: feat(vault): @elizaos/vault — cross-platform secrets vault + Settings UI integration](https://github.com/elizaos/eliza/pull/7197) by Dexploarer - Status: merged - Significance: Introduces robust secret management and encryption at rest, replacing plaintext storage in config.env.
- [Pull_request #7235: chore: add cloud and plugins, remove rust and python](https://github.com/elizaos/eliza/pull/7235) by lalalune - Status: open - Significance: Major architectural simplification and repository consolidation.
- [Issue #7245: telegram: milady wrapper + @elizaos/plugin-telegram both poll the same bot — race causes silent message loss](https://github.com/elizaos/eliza/issues/7245) by Sw4pIO - Status: open - Significance: Critical bug causing inconsistent bot responses due to duplicate polling instances.

#### Overall Focus
- Consolidating core framework to ESM standards and stabilizing runtime environments across Linux headless servers and Windows Server 2025.

### Discord Updates
- **#discussion:** Focus on the upcoming v3 architecture, including task issuance to Codex/Claude and the financial history of the project development funding. (Key Participants: shawmakesmagic, marianodim)
- **#partners:** Establishment of the 'Eliza Army Steering' group to coordinate community and partner efforts to maintain project momentum. (Key Participants: odilitime, rabbidfly)

### User Feedback
- Developers are reporting persistent 401 Unauthorized errors in Anthropic requests when using OAuth due to missing stealth fetch interceptors in the build process. (Sentiment: negative)

### Strategic Insights

#### Memory Rot Awareness
The identification of 'memory rot' highlights a critical limitation in current RAG architectures for long-lived autonomous agents.

*Implications/Questions:*
  - Should the reconciliation pass become a core required service for all ElizaOS agents?

#### Open-Source vs. Platform Branding
Clarification of ElizaOS as an 'OS/Framework' (Linux model) versus consumer platforms like Orbofi (Shopify model) establishes a clear B2B/Dev focus.

*Implications/Questions:*
  - Does the inclusion of the Milady App Store deviate from the pure OS philosophy?

### Market Analysis
- NDA-bound exchange listing discussions confirmed as ongoing but non-public. (Relevance: Direct impact on community sentiment and token liquidity expectations.)