## ElizaOS Weekly Newsletter (2026-03-06 → 2026-03-12) ### 1) Executive Summary **1) Babylon is live (first 50,000 users) and expanding.** Babylon successfully launched to an initial cohort of **50k users** and is now **opening up more broadly**. A nice touch for ecosystem awareness: the **elizaOS.news ticker** is already embedded in the Babylon experience at: https://play.babylon.market/ticker **2) Eliza Framework v2.0.0 hit an “alpha published” milestone.** The team shipped the **Eliza 2.0.0 alpha**—a concrete marker that the architecture work is real and progressing, even while several work-in-progress items remain. **3) Better “signal compression” is underway (video briefings + dev tooling).** To address the community’s repeated request for clearer updates, Jin is building a **modular video briefing system** (daily/weekly/monthly formats), while Odilitime demonstrated a **git branch story tool** that can summarize how branches evolved across 0.x → 1.x → 2.x. --- ### 2) Development Updates (Framework, Apps, Infra) **Eliza 2.0.0 alpha: architecture is shifting toward smarter scheduling and deployment options.** The most notable technical direction discussed this week is a push toward **more structured orchestration of LLM calls** and more flexible infrastructure: - **Prompt batching / unified scheduling concept (v2 direction):** After reviewing a large plugin set, Odilitime described consolidating three categories of calls—**init prompts**, **autonomous calls**, and **evaluator calls**—into a single configurable scheduler. The goal: optimize differently for **frontier models vs. local models**, reduce overhead, and improve determinism. - **Serverless-style patterns emerging from implementation work:** The team is discussing options like **lazy-loading services**, **outsourcing work to external systems**, and **in-memory persistence** to avoid expensive reinitialization. - **Embeddings as a cloud microservice (xfn-framework):** A concrete proposal: implement a **cloud REST endpoint** that handles embedding computation *and* persistence. This decouples embeddings from the main app runtime and can make scaling and ops more manageable (especially if you want to swap providers or isolate workloads). **Eliza app progress continues.** Beyond the framework, the **Eliza application** is still in active development, with multiple features reportedly nearing completion. (No detailed changelog was shared in Discord, but the status updates were explicit that work is ongoing.) **Milady / ecosystem integrations: real-world configuration pain points surfaced.** In community dev chatter: - **Neon DB integration**: BinaryCookies tracked down where to configure Neon database settings (in the **`env` section of a JSON config**) but still ran into **permissions/capabilities** issues—good reminder that “docs-first config” matters as much as code. - **Automation triggers & timed interactions**: The community pointed developers toward existing autonomous agent examples and trigger systems to implement scheduled Discord interactions. **AEP (Autonomous Economy Protocol) plugin announcement: on-chain payments + reputation.** TraderTomson introduced **AEP**, positioned as a marketplace/payment+reputation layer for agents on **Base** using **AGT** tokens. It includes TypeScript actions like `REGISTER_AGENT`, `BROWSE_MARKET`, `PROPOSE_DEAL`, and reputation checks—aimed at making agent-to-agent commerce more standardized. --- ### 3) Community Spotlight (Notable Contributions & Discussions) **Jin’s video briefing system: turning Discord entropy into weekly clarity.** Jin shared an evolving system to generate **MP4 briefings** with a modular “any segment can become a clip” approach. Planned upgrades include: - **Temporal analysis** to extract narratives and patterns for weekly/monthly recaps - **Interviews with builders** to avoid repetitive “daily status drone” updates - Potential **Grok integration** to pull relevant ecosystem news from X This is directly aligned with what the community asked for most loudly this week: *more consistent, higher-signal communication*. **Odilitime’s git branch storytelling tool (PRR).** A standout “meta-dev” contribution: a tool that analyzes git branches and generates a narrative of development progression across versions. It was demoed using elizaOS 0.x/1.x/2.x branches and shared publicly here: https://github.com/elizaOS/prr/pull/5 **Security-first culture in action: wallet isolation + scam warning.** Two important community moments: - **Wallet safety architecture:** Odilitime emphasized a security-by-isolation approach—keeping **LLMs fully separated from addresses and private keys** (via Spartan infrastructure) to reduce prompt-injection-to-drain risk. - **Phishing attempt response:** A scammer tried to convince users Discord “requires wallet linking.” The team clearly confirmed: **Discord does not require wallet linking**. If anyone DMs you claiming otherwise, assume malicious intent. --- ### 4) Token Economics (AI16z, ELIZAOS, auto.fun) **Market sentiment: community concern remains high.** Discussion in 💬-discussion was dominated by frustration around **token underperformance**, references to a **new ATL**, and questions about communication gaps, selling pressure, and whether builders had left. Team members responded directly: development is active (Babylon + Eliza v2 alpha + app work), and the project is operating as an **open-source model** with a core team plus community contributors. **AI16z → ELIZAOS migration: process reopened (not fully finalized).** Odilitime indicated that additional migrations may be allowed, but the workflow is still being finalized. The current guidance shared publicly: - Users should **DM their wallet address** - Provide **proof of holding** during the **September snapshot** **$ELIZAOS “holders system” restoration was mentioned as an objective.** No implementation details were posted this week, but it’s on the list of commitments tied to improving holder experience and communications. **auto.fun:** no explicit product changes shared in the provided logs. There were no specific auto.fun release notes in Discord summaries this week. If you’re building around auto.fun, consider this a “quiet week” publicly—watch for updates as the team improves outward comms and ships the next Eliza milestones. --- ### 5) Coming Soon (What to Watch Next) - **Eliza 2.0.0 alpha → more complete alpha:** continued iteration to stabilize the new architecture and unblock dependent work (including better outbound comms tooling and integrations). - **Prompt batching / scheduler work:** expect more visible framework changes as the unified scheduling concept turns into code and configuration surfaces. - **Embeddings REST microservice:** likely an infra track that could materially improve scalability and modularity for builders running production agents. - **Video briefings v1:** daily → weekly/monthly formats, plus experiments with interviews and “highlight reels” to increase signal. - **Babylon expansion:** broader user rollout and deeper visibility via the in-product ticker. - **Migration process clarity:** expected next step is a more formalized, less manual workflow for ai16z → elizaOS conversions. --- ### 6) Resources (Links & References) - **Babylon ticker (elizaOS.news):** https://play.babylon.market/ticker - **Git branch story tool (PR):** https://github.com/elizaOS/prr/pull/5 - **Autonomous agents examples (timers/triggers reference):** https://github.com/elizaOS/examples/tree/main/autonomous/typescript - **Milady repository (trigger systems mentioned):** https://github.com/milady-ai/milady - **AEP SDK (announcement reference):** `autonomous-economy-sdk` (npm package name shared in Discord) - **Key Discord threads (summarized):** - 💬-discussion (project status, Babylon, v2 alpha, comms, phishing warning) - 💬-coders (wallet isolation best practice) - xfn-framework (embeddings REST microservice idea)