# ElizaOS Weekly Newsletter (Mar 8–Mar 14, 2026)

## 1) Executive Summary

**1) Eliza 2.0.0 Alpha is out, and momentum is visible across the stack.**  
This week brought a tangible “we’re shipping” signal: the **Eliza 2.0.0 alpha** was published, alongside ongoing work toward the Eliza app experience. The alpha release also sparked deeper conversations about runtime architecture and plugin lifecycle correctness—exactly the kind of hard engineering work that makes the next releases sturdier.

**2) Babylon Market launched to its first 50,000 users (now expanding).**  
Babylon’s rollout is a meaningful ecosystem milestone: real users, real distribution, and a live surface area for ElizaOS-adjacent content (including the **elizaos.news ticker**). This is the sort of launch that forces systems to mature quickly—operationally and product-wise.

**3) Clearer token/business narrative + heightened security posture.**  
The team reiterated the core economic thesis: **cloud services drive revenue → revenue drives buybacks of elizaOS tokens** (not Milady tokens). In parallel, the community dealt with **migration deadline reality** and a renewed wave of **scam attempts**, prompting strong, repeated reminders about wallet safety and seed phrase hygiene.

---

## 2) Development Updates

### Runtime & plugin architecture: refactor discussions heat up
A major **runtime refactor proposal** was shared (via HackMD) with a near-term feedback deadline. The core issue being addressed: **plugin initialization side-effects + parallel init = race conditions**.

- **The concrete bug pattern:** `plugin-sql` registers its DB adapter as a side-effect during `init()`, while other plugins initialize in parallel. This can cause `plugin-personality` (or others) to run before the DB adapter exists.  
- **Current workaround (acknowledged as defensive, not ideal):** some apps manually pre-register `plugin-sql` before `initialize()`.  
- **Proposed direction:** make infrastructure dependencies explicit—e.g., **require the DB adapter as a constructor argument** rather than relying on side-effect registration.

Why this matters: it’s less about one plugin and more about making ElizaOS **composable and deterministic** as the plugin ecosystem grows.

### Scheduling agents: cron-based wakeups and Discord posting automation
In #coders, there was a practical thread on **how to run agents on a schedule** (e.g., posting to Discord at intervals without manual triggers):

- **ElizaOS v2.x:** recommended **`plugin-cron`** for scheduled tasks and “agent wake-up” behavior.  
- **ElizaOS v1.x:** recommended **`plugin-heartbeat`** as the more compatible approach.  
- Odilitime shared working examples from the Spartan codebase (including patterns like `tsk_discord_post.ts` and DM utilities), and community members discussed how to adapt newer scheduling patterns to **ElizaOS 1.7.2**.

Takeaway: autonomous cadence (posting, polling, maintenance tasks) is becoming “table stakes,” and the community is converging on repeatable scheduling primitives.

### Ecosystem tooling: git branch “story” generation
A developer tool dropped that’s especially useful for release management and historical analysis: a **git branch analysis tool** that generates a narrative “branch story,” demonstrated across ElizaOS 0.x → 1.x → 2.x.

- Reference implementation: https://github.com/elizaOS/prr/pull/5

This could become a useful internal/community standard for summarizing branch intent, change arcs, and migration implications.

### New plugin: PumpFun tokenized agent buyback payments (Solana)
Meme Broker announced a new plugin integrating **PumpFun’s automated buyback system** for agent payments on Solana. While early, it’s notable for two reasons:
1) it’s a concrete example of **agent monetization plumbing**, and  
2) it intersects with broader “tokenized agent” narratives that also touch auto.fun discussions.

---

## 3) Community Spotlight (Discord)

### Agent registry “in the wild”: aiprox.dev
A standout community moment: lightningprox shared an **open agent registry with autonomous orchestration** at **aiprox.dev**, and reported a milestone that feels very “agentic” in spirit—an external agent **autonomously discovered the registry and attempted self-registration** without prompting.

Key features discussed:
- public REST API for registration and discovery (`/api/agents/register`, `/api/agents`)  
- usage-based ratings and an auto-approver scoring pipeline (1–10)  
- multiple payment rails (Lightning / Solana / x402)  
- ~14 live agents at the time of sharing  
- integration with agentskills.io via a `skill.md` file for discovery

This is exactly the kind of “ecosystem glue” that makes ElizaOS more than a framework: it becomes a network.

### Content & communications: video briefing system in progress
Jin outlined a **modular video briefing system** to turn Discord/Telegram chatter into digestible media:
- daily objective updates (with weekly/monthly planned)
- modular MP4 generation for any segment
- “temporal analysis” to pull patterns/narratives over time
- planned builder/project interviews for variety
- potential integration with Grok for X/news scanning

Community feedback pushed toward **highlights + variety** over monotonic daily cadence—an important signal about how members want to consume project progress.

### Security & moderation: scams, wallet safety, and channel hygiene
- Multiple scam warnings were issued this week, including phishing attempts claiming **Discord requires wallet linking** (it does not).  
- Migration-related social engineering intensified as some users sought “late migration” paths. Moderators and members repeatedly warned: **never share seed phrases**, and be skeptical of “support bots.”

---

## 4) Token Economics (AI16Z → elizaOS, auto.fun, and value accrual)

### Migration status: closed (and scammers are exploiting confusion)
The community reiterated that the **AI16Z → elizaOS token migration window is closed** (permanent close date cited in discussion: **Feb 4, 2026**, after a 3-month window). Users asking for exceptions were told clearly: **there is no legitimate migration path right now**, and anyone offering one is likely scamming.

### Business model clarity: cloud profits → elizaOS buybacks
A key clarification that helped cut through noise:
- **Primary business model:** cloud services (including Milady cloud operations)  
- **Value accrual:** profits go toward **buybacks of elizaOS tokens** (not Milady tokens)  
- **Team allocation:** discussed as **10% vested over multiple years**, with team members noting minimal selling pressure recently

### auto.fun / tokenized agents thread
While there wasn’t a formal auto.fun release note in the data, the week’s “tokenized agent” discussions (including the PumpFun buyback plugin) suggest a growing focus on **payment rails, buybacks, and sustainable agent monetization**—all highly adjacent to auto.fun’s broader direction.

---

## 5) Coming Soon

- **Milady app target:** ~2 weeks from Mar 12 (watch for release candidate chatter and onboarding docs).  
- **Runtime refactor:** feedback window closing soon; expect follow-up PRs that make plugin dependency injection more explicit and reduce init-time races.  
- **Embeddings as a cloud service:** discussion continued around a REST-based embeddings endpoint handling compute + persistence—likely a stepping stone toward more modular cloud primitives.  
- **Better community updates:** video briefings expanding from daily experiments into weekly/monthly formats (and potentially Telegram mirroring).  
- **Migration reopening (not promised):** a list of affected users is being maintained for any future reconsideration—treat this as “possible,” not scheduled.

---

## 6) Resources

- **Babylon Market ticker (elizaos.news):** https://play.babylon.market/ticker  
- **Git branch story tool (PR):** https://github.com/elizaOS/prr/pull/5  
- **Agent registry shared by community:** https://aiprox.dev  
  - discussed endpoints: `/api/agents/register`, `/api/agents`  
- **Runtime refactor proposal:** shared on HackMD in Discord (check pinned/linked message from Odilitime)  
- **Docs/website cloud content (mentioned PR):** elizaos.github.io PR **#243** (referenced in Discord)  
- **Security reminders:**  
  - Discord does **not** require wallet linking  
  - never share seed phrases; ignore “support bots” and off-platform migration offers