# ElizaOS Weekly Newsletter (2026-03-18 → 2026-03-24) ## 1) Executive Summary **1) Milady app pushed forward (weekend sprint).** The core team confirmed **active Milady app development through the weekend**, with **Odilitime jumping in directly** to help unblock progress. There’s **no public launch date yet**—the consistent message is: *it ships when it’s ready*. **2) Agent monetization hit a new milestone: on-chain, autonomous, and live.** A community-shared Eliza plugin enables **autonomous agent monetization on Base**, including an **on-chain marketplace** where agents can register, advertise services, hire each other, and **settle payments in AGT**—all without human intervention. **Season 1 is live** with a **50M AGT pool** aimed at early adopters. **3) Community aligned (and challenged) around token + communication realities.** This week surfaced a clear theme: members want **more explicit token utility and clearer product-to-token linkage**, especially amid **sharp price drawdown concerns**. Team/community helpers reiterated where official updates live (weekly videos + daily update channels) and encouraged focusing on delivery milestones rather than rumor cycles. --- ## 2) Development Updates (Technical) While we don’t have a full GitHub merge log snapshot for this specific week in the provided data, Discord discussions surfaced several concrete technical threads worth tracking: ### Milady app: “building mode” remains active - **Status:** Ongoing build; team worked through the weekend. - **Signal:** Odilitime noted direct participation, suggesting the team is treating remaining work as hands-on engineering rather than only coordination. - **What we’re still missing publicly:** a changelog (features completed vs. blocked), release candidate criteria, and a clear “definition of done.” ### Agent monetization plugin (Base + AGT) A community announcement detailed a plugin that: - Lets agents **register on an on-chain marketplace** - Post services and get **hired by other agents** - Receive **AGT payments autonomously** (no human in the loop) - Kicked off with **Season 1** incentives: **50M AGT pool** Why this matters: it’s a credible “agent-native” economic loop—*agents paying agents*—which is exactly the kind of utility narrative community members have been asking to see more of across the ecosystem. ### Community-built multi-agent trading system (seeking partner) One builder (Naman) shared plans for a **multi-agent autonomous crypto trading system**, targeting: - **24/7 trading** - A **local 200–500B parameter LLM** - Needs: **model optimization, fine-tuning, performance monitoring** - Proposed partnership: **10% profit share** for an AI/ML technical collaborator Even if this is not a core ElizaOS deliverable, it’s an important community signal: people are actively trying to build “serious” agent systems on/around ElizaOS, and they need best-practice guidance on reliability, evals, and deployment. --- ## 3) Community Spotlight (Discord) ### The “Milady timeline” loop—and why it keeps coming up Multiple community members asked variations of: **“When will Milady be online?”** Odilitime’s consistent answer: **no date**, launch **when it’s ready**, and confirmation of **weekend work**. Takeaway: the community isn’t just asking for hype—they’re asking for *planning signals*. Even a lightweight public checklist (alpha/beta gates, known blockers, what “ready” means) would likely reduce repeated friction. ### Communication expectations vs. what’s being delivered A recurring tension: members feel updates exist but don’t answer their *core questions* (utility, roadmap certainty, token alignment). Team members pointed to: - **Weekly video updates** (“cronjob”) - **Daily updates** in a dedicated channel Community suggestion that emerged organically: when “no communication” claims appear, respond with a link to the official updates channel so newcomers can orient quickly. ### Ecosystem architecture clarity: ElizaOS vs. Milady vs. OpenClaw A helpful clarification resolved a key misconception: - **ElizaOS is the base “operating system for agents.”** - **Milady is built on top of ElizaOS** (not a replacement). - **OpenClaw agents can exist within Milady**, meaning these pieces can be complementary rather than competitive. That architecture framing is important—especially for builders deciding where to invest time and how to think about compatibility. --- ## 4) Token Economics (AI16z token + auto.fun) ### AI16z token: sentiment and open questions This week included blunt community concern about token performance, including comparisons between previous highs and current price levels. The dominant requests from holders were: - **Concrete token utility** tied directly to products being built - Better articulation of **why someone would buy/hold the token** - Market-structure asks: **stronger CEX listings** and **perpetual futures** were raised as potential catalysts (community view) Team/community guidance shared publicly emphasized: - Follow **official team updates** - Avoid spiraling on rumors/FUD - A belief that **2026 will be a significant year for agentic AI**, with optimism that delivery will matter more than short-term noise ### auto.fun: minimal explicit updates in the provided feed There wasn’t a specific auto.fun product update captured in this week’s provided Discord summaries beyond community presence/roles. If auto.fun has shipped changes, they weren’t reflected in the data snapshot here—so consider this a call for contributors to share links in the updates channel for inclusion next week. --- ## 5) Coming Soon (What to Watch Next) **Milady app launch readiness signals** - Expect continued “when it’s ready” messaging unless/until a public checklist is posted. - What the community should watch for: onboarding flow, stability, and how Milady exposes or packages ElizaOS agent capabilities. **Marketplace/monetization adoption** - If the Base marketplace plugin gains traction, we may see: - Standardized “agent service” schemas - Reputation/verification patterns for agents selling services - Real demand for escrow, dispute handling, and identity primitives **Potential exchange outreach** - BitMart’s listing team reached out requesting a business cooperation discussion. No decisions were documented this week, but it’s a thread to monitor. **A push toward clearer token utility** - Community pressure is consistent and specific: link token mechanics to shipped features (not just future intent). Expect this to remain a top community topic until addressed with concrete integrations. --- ## 6) Resources (Links & Pointers) **Core documentation / “where is the whitepaper?”** - Roadmap (GitHub): https://github.com/elizaOS/roadmap - Academic paper (arXiv): https://arxiv.org/abs/2501.06781 **Key Discord discussion context (week highlights)** - Discussion channel thread (March 23 context, including Milady status + token sentiment + BitMart outreach): https://discord.com/channels/1253563208833433701/1253563209462448241 **Build/participation opportunities surfaced this week** - Agent monetization marketplace plugin announcement (Base + AGT, Season 1 live with 50M AGT pool) — shared in Discord (watch for a repo/PR link in follow-ups) - Multi-agent autonomous trading system collaboration request — shared in Discord (AI/ML optimization + monitoring, profit-share proposal) --- If you want next week’s newsletter to include deeper engineering detail (commits, PRs, shipped artifacts), the fastest path is: drop **links to PRs, releases, or demo endpoints** into the updates channel so they’re easy to attribute and summarize.