## ElizaOS Weekly Newsletter (2026-04-29 → 2026-05-05) ### 1) Executive Summary This week was a strong “ship + scale” sprint across core infrastructure, Cloud, and model work: 1. **ElizaOS v2.0.0-beta.0 landed on GitHub** alongside continued “housekeeping” work—signaling the team is actively pushing the codebase toward the next major release cycle. 2. **Security + operational maturity leveled up** with the merge of **`@elizaos/vault`**, bringing cross-platform secrets management (OS keychain + headless fallbacks) integrated directly into Settings UI and runtime operations. 3. **Ecosystem reach expanded** with major platform work: **Slack connector migration into the monorepo**, and **Eliza Cloud monetized app domains + app-scoped chat** groundwork—paving the way for revenue-bearing apps rather than “just agents.” --- ### 2) Development Updates (Core, Cloud, Plugins) #### Core framework & repo structure - **Monorepo consolidation took a big step** with **“add cloud and plugins, remove rust and python”** merged into `elizaos/eliza` ([#7235](https://github.com/elizaos/eliza/pull/7235)). Net effect: fewer moving parts, more consistent workflows, and a clearer “single source of truth” for core + plugins + Cloud-related code. - **Self-hosted connectivity improvements** shipped via **CORS, bearer auth, and cross-platform build fixes** ([#7212](https://github.com/elizaos/eliza/pull/7212)). This improves the story for people running ElizaOS agents behind custom domains and connecting web/mobile/desktop surfaces reliably. #### Secrets & credential safety: `@elizaos/vault` - **`@elizaos/vault` merged** ([#7197](https://github.com/elizaos/eliza/pull/7197)), introducing: - Encryption-at-rest (AES-256-GCM) - Default OS keychain storage (macOS/Windows/Linux Secret Service) - Headless Linux fallbacks via passphrase-derived master keys - Settings UI integration (vault-first reveal + write-through mirroring) - A key stability follow-up also merged: **skip OS keychain on headless Linux to prevent segfaults** ([#7230](https://github.com/elizaos/eliza/pull/7230)). If you run servers in minimal environments, this is a meaningful reliability upgrade. #### Connectors & plugins - **Slack connector migrated into the monorepo** ([#7375](https://github.com/elizaos/eliza/pull/7375)). This brings `@elizaos/plugin-slack` in line with other first-party connectors and adds a large test suite (120 tests) plus a full set of Slack actions/providers. - Automation and workflow UX continued to harden: - n8n clarification loop work (route + UI support) landed through a series of improvements (e.g., clarification roundtrip + quick-pick UI) including [#7316](https://github.com/elizaos/eliza/pull/7316), [#7341](https://github.com/elizaos/eliza/pull/7341), and follow-up fixes. #### Eliza Cloud: monetized apps path - **Cloud gained support for monetized container app domains** ([#7376](https://github.com/elizaos/eliza/pull/7376)), including app-scoped chat (`/api/v1/apps/:appId/chat`) and Cloudflare-managed domain flows. This is part of the broader push toward *apps that can earn revenue* (and therefore support sustainable token mechanics later). - Note: automated review notes flagged a few **P1 correctness/auth edge cases** in this area. If you’re building on Cloud APIs right now, keep an eye on follow-up patches and test your auth + reconciliation flows carefully. --- ### 3) Community Spotlight (Discord Highlights) #### Model development: eliza-1 training progress Shaw shared a dense, genuinely exciting update on **training “eliza-1”** as a **general-purpose model**: - **Base model:** Qwen - **Trained in:** the Eliza harness (purpose-built training setup) - **Performance work:** *dflash speculative decoding* - **Reasoning efficiency:** *caveman compression* applied to “thinking” - **Deployment practicality:** *turboquant* quantization path These are the kinds of “under the hood” optimizations that tend to matter more than flashy demos once you’re running agents at scale. #### Builder wins: elizaOK made Top 20 Big congrats to **Baoger**—their community project **elizaOK** was selected as a **Top 20** entry in the Fourmeme Hackathon AI Sprint (Group 3). They asked the community to vote via Binance Square ahead of the May 8 deadline (see Discord thread below). #### Culture & expectations: builders > speculators A notable conversation (driven by Shaw) reframed token-holder expectations: - Token holders are not treated like traditional equity investors. - **Buybacks require revenue**; demanding them pre-revenue is structurally harmful. - The priority remains **shipping revenue-generating products** (V3 launch, Eliza Cloud, Milady app) and growing a builder community. #### Security vigilance: scam warnings Several users flagged scam attempts—especially around **token migration** and **bridging links**. A reminder: rely on pinned docs and official links, and treat DMs as hostile by default. (Community members also requested moderator action to ban scammers when spotted.) --- ### 4) Token Economics (AI16z Token + auto.fun) #### Bridging & migration questions (BSC ↔ Solana) Token operations were a recurring topic this week: - Users asked how to **bridge ElizaOS tokens from BSC to Solana**. - Community responses suggested **Wormhole** or **deBridge** as bridging options (always verify contract addresses and official endpoints before sending funds). There was also an open question—“Is there any way to migrate ai16z to ElizaOS?”—that surfaced amid scam attempts. If/when an official migration path exists, expect it to be announced through **official channels with auditable links**; until then, treat “migration” URLs as high-risk. #### Price talk (kept secondary) Community chatter noted strong movement (V3 discussed as up ~90–130% in conversation), but the dominant narrative from core contributors stayed anchored on product execution and revenue. #### auto.fun No explicit engineering or rollout update for **auto.fun** appeared in the provided discussions this week. The broader direction remains clear, though: **revenue-first product releases** are the prerequisite for any meaningful token-mechanism evolution. --- ### 5) Coming Soon Here’s what the community should watch for next: - **ElizaOS V3 launch** planning (including community PR/marketing coordination mentioned in Discord). - **Eliza Cloud expansion** as the “apps that earn” substrate (domains, app auth, app-scoped chat). - **Milady app** as a key revenue driver repeatedly referenced in roadmap conversations. - Continued progress on **eliza-1** training (especially whether the decoding/quantization stack delivers real-world latency and cost improvements). --- ### 6) Resources (Links & Pointers) **Discord discussions (high signal)** - Model + bridging + scam warnings (2026-05-05): https://discord.com/channels/1253563208833433701/1253563209462448241 - Vision/roadmap framing + repo pointers (2026-05-03): *(see summary thread content)* **Key PRs merged this week** - `@elizaos/vault` (secrets vault + Settings integration): https://github.com/elizaos/eliza/pull/7197 - Repo consolidation (cloud + plugins; remove rust/python): https://github.com/elizaos/eliza/pull/7235 - Self-hosted CORS + bearer auth + build fixes: https://github.com/elizaos/eliza/pull/7212 - Slack plugin migration into monorepo: https://github.com/elizaos/eliza/pull/7375 - Cloud monetized container app domains: https://github.com/elizaos/eliza/pull/7376 **Repos mentioned for builders** - `plugin-auto-trader` - `plugin-social-alpha` - `spartan` If you’re looking for a high-leverage way to contribute right now: test the newest beta paths, help validate Cloud domain/app flows, and keep tightening the “safe onboarding” surface area (docs + anti-scam hygiene).