# ElizaOS Weekly Newsletter (2026-03-07 to 2026-03-13) ## 1) Executive Summary **1) Eliza 2.0.0 alpha is out, and the “next architecture wave” is underway.** This week marked a concrete milestone with the **Eliza 2.0.0 alpha release**, while core contributors simultaneously kicked off a deeper push on runtime architecture—especially around plugin initialization, infrastructure registration, and making the framework more predictable at scale. **2) Babylon launched to its first 50,000 users and is now opening wider.** Community members confirmed **Babylon’s initial rollout** is live and expanding, including a public ticker experience at **https://play.babylon.market/ticker**. It’s a meaningful “real users, real load” moment for the ecosystem. **3) Clearer ecosystem flywheel: Milady app + cloud → buybacks for elizaOS token.** The team reiterated the near-term product cadence—**Milady app targeting ~2 weeks**—and clarified the business model: **cloud profits are intended to fund buybacks of elizaOS tokens** (not Milady token). This was one of the most important alignment points in community discussion. --- ## 2) Development Updates (Technical) ### Runtime refactor proposal (high-impact, feedback requested) Odilitime shared a significant proposal to address the **AgentRuntime being a ~6,273-line “god object”** and to fix a class of issues stemming from **parallel plugin initialization**. **Key issue identified: plugin initialization race condition** - `plugin-sql` currently registers its database adapter as a **side-effect in `init()`**. - Because plugin init runs concurrently, dependent plugins (e.g., `plugin-personality`) can execute **before** the DB adapter is available. - A defensive workaround in *milaidy* manually pre-registers `plugin-sql` before `initialize()`, but the consensus is this treats the symptom, not the cause. **Proposed direction** - **Make the database adapter a required constructor argument** (explicit dependency injection), rather than relying on plugin side-effects. - **Split runtime setup logic out of the runtime module**, externalize components, and reduce hidden coupling. - A community request was emphasized: keep the refactor **minimal in API complexity** and **low in downstream breakage**. > There’s an explicit deadline for feedback (“by Sunday”), after which implementation is expected to proceed. ### Prompt batching subsystem (v2.0.0 branch direction) After reviewing **50–60 plugins**, Odilitime consolidated improvements into a new **prompt batching** subsystem: - Unifies **init LLM calls**, **autonomous LLM calls**, and **evaluator calls** into a **single configurable scheduler** - Intended to optimize for both **frontier models** and **local models** - Builds on existing “dynamicPromptExecution” patterns already seen in newer autonomous systems This is a big deal for anyone running multiple plugins or agent loops: it targets cost control, latency reduction, and predictability. ### Cloud infrastructure & pipeline tracking With cloud now public-facing, the **`elizaos/cloud` repository** was added to the tracked repos in the pipeline configuration (with **`dev` as default**). This is a small line item that signals a bigger shift: cloud is becoming first-class in the delivery pipeline and documentation. ### Tooling: git branch “story” generator A dev tool for generating narrative summaries of git branches was demonstrated and shared via: **https://github.com/elizaOS/prr/pull/5** If you’re trying to understand deltas between 0.x → 1.x → 2.x (or explain them to others), this is a practical contributor tool. --- ## 3) Community Spotlight (Discord) ### lightningprox’s open agent registry (aiprox.dev) One of the most exciting builder updates this week came from **lightningprox**, who shared an **open agent registry + orchestration** system at **https://aiprox.dev**. **Notable features** - Agents can **self-register** - Agents are **rated by real usage** - Multi-rail payments: **Lightning / Solana / x402** - An **auto-approver pipeline** scores new registrations **1–10** to filter low-quality submissions - **14 live agents** at the time of discussion **The “wow” moment:** an external agent autonomously discovered the registry and attempted self-registration without being prompted—exactly the kind of emergent behavior many in this community are building toward. **Discovery integration shipped fast** Odilitime suggested adding a `skill.md` file for agentskills.io discovery, and lightningprox implemented it immediately (a great example of rapid community iteration). ### New builder intro: genife A new member, **genife**, introduced themselves as an AI & Full-Stack Engineer with experience in production-grade AI (LLM orchestration, RAG, multi-agent, DSPy/LangChain/AutoGen/CrewAI). If you’re shipping plugins or infra and want another set of hands, this is a strong profile to connect with. ### Security reminders (community-protecting wins) Two separate scam patterns were flagged: - A fake “support ticket bot” routing users to a site requesting **seed phrases** - A phishing attempt claiming Discord requires **wallet linking** (it does not) The takeaway the team repeated: **never share seed phrases**, and treat “support bots” as hostile unless verified. --- ## 4) Token Economics (AI16Z / elizaOS token + auto.fun) ### Cloud-first value accrual: buybacks for elizaOS The clearest tokenomics statement this week: - **No direct token utility is live right now** for holders. - The business model is centered on **cloud services**, with **profits intended to fund buybacks of elizaOS tokens**. - The team emphasized long-term alignment: they hold **~10% vested over multiple years**, and Odilitime stated he **hasn’t sold in the past two months**. ### AI16Z → elizaOS migration status + scam warning - Migration was stated as **permanently closed on Feb 4, 2026** after a 3‑month window. - Some users are still requesting help; Odilitime is maintaining a list of affected wallets in case reopening becomes possible, but indicated attempts to reopen have not succeeded so far. - Important: scammers are exploiting migration confusion—do not connect wallets or enter seed phrases on random “support” sites. ### auto.fun developments No concrete new auto.fun shipping notes were captured in this week’s discussions. If auto.fun is part of what you’re tracking, this week was more about **clarifying the cloud→buyback flywheel** and cleaning up migration/security narratives than announcing new auto.fun mechanics. --- ## 5) Coming Soon - **Milady app release target:** ~2 weeks from March 12 discussion (watch for launch readiness updates). - **Runtime refactor execution:** feedback window closing Sunday; expect implementation steps and possible migration guidance for plugin authors. - **Fix for plugin-sql initialization model:** likely moving toward explicit adapter injection (less “magic,” fewer races). - **Embeddings as a cloud service:** discussion continued around a REST endpoint for embeddings compute + storage—suggesting a microservices direction. - **Eliza app:** still in active development, with multiple WIP items nearing completion. - **More consistent comms:** elizaOS.news + video briefing workflows are being built to reduce “Discord-only” context. --- ## 6) Resources (Links) - Babylon ticker: https://play.babylon.market/ticker - elizaOS.news (update workflow hub referenced in discussions): https://elizaos.news - Agent registry (aiprox): https://aiprox.dev - Registry endpoints mentioned: `/api/agents/register`, `/api/agents` - Git branch story tool PR: https://github.com/elizaOS/prr/pull/5 - Docs PR (cloud content): **elizaos.github.io PR #243** (referenced in Discord; check the repo PR list for review/merge)