# ElizaOS Weekly Newsletter (2026-03-16 → 2026-03-22) ## 1) Executive Summary **1. Autonomous agent monetization arrived (community-led).** TraderTomson shipped and announced a new Eliza plugin that lets agents **earn autonomously on Base**: agents can register on an **on-chain marketplace**, post services, get hired by other agents, and **receive AGT payments without human intervention**. Season 1 is already live with a **50M AGT** incentive pool for early adopters. **2. Babylon integration narrative sharpened: airdrop + buyback mechanics.** Community questions about “what Babylon actually does for ElizaOS” got a concrete answer: the integration is expected to include a **community airdrop** and to **drive ElizaCloud buybacks**—one of the clearest tokenomics hooks discussed this week. **3. Ecosystem architecture confusion cleared up (Milady vs ElizaOS vs OpenClaw).** A recurring misunderstanding was resolved publicly: **ElizaOS is the foundational agent OS**, and **Milady is built on top of ElizaOS** (not a replacement). Likewise, **OpenClaw agents can exist within Milady**, so these pieces are complementary rather than competing. --- ## 2) Development Updates ### Agent Monetization Plugin (Base + on-chain marketplace) - **What it does:** Enables agents to autonomously: - register on a marketplace - list services - hire (and be hired by) other agents - settle payments in **AGT tokens** on Base - **Why it matters:** This is one of the most “end-to-end” demonstrations of agent autonomy in the ecosystem: discovery → contracting → payment, all without a human in the loop. - **Current status:** Season 1 is live, with incentives (see Token Economics). ### Milady App: steady progress, not yet “marketing ready” - The team reiterated a **“ready when ready”** posture: releases exist, but polish is still in progress and not considered launch-campaign-ready yet. - **Noted issues to resolve:** - **GPG key** concerns - **SHA256 checksum** problems These are the kinds of release-integrity details that become critical once distribution ramps. ### ElizaOS + ElizaCloud stack: disk image upload bug under investigation - Current setup was described as **elizaos 1.x CLI + elizacloud**. - A specific issue surfaced: users reported uploading a disk image successfully, but **nothing appeared server-side** (“sent, but not received”). Investigation is ongoing—this is worth watching because it impacts developer experience and deployment workflows. ### WIP demos: personalities + holographic display experiments Magicyte shared work-in-progress demos showing: - AI characters with **distinct personalities** - A **Milady hologram** running on a Looking Glass Go display There was also early discussion about potentially shipping these as **standalone units** or **Mac Mini plug-and-play** kits—still exploratory, but a compelling direction for “agent embodiment” and demoability. --- ## 3) Community Spotlight (Discord) ### Big discussion: communication, expectations, and token utility The community spent meaningful time discussing **project communication** and what “good progress” should look like. Key themes: - Some members feel that weekly videos (“cronjob”) and daily update posts exist, but **don’t address the questions people care about most** (especially token utility and timelines). - There’s a strong desire for **clearer utility narratives**: community members repeatedly asked, “What’s one use case of this token?” and “Why buy it?”—and those questions remained largely unresolved in-chat. **Takeaway:** The community isn’t just asking for *more* communication; they’re asking for communication that is **more directly tied to utility, roadmap milestones, and measurable outcomes**. ### Architecture clarification: ElizaOS as the base layer A helpful technical clarification landed well: - **ElizaOS = the operating system for agents (base layer)** - **Milady = application layer built on ElizaOS** - **OpenClaw ≠ competitor to Milady**; OpenClaw agents can exist inside the Milady environment This kind of “stack map” explanation reduces ecosystem infighting and helps builders choose where to contribute. ### Helpful resources and support moments - When asked for a “whitepaper,” community members guided the user to official docs, and Odilitime clarified that **there is no traditional whitepaper**, pointing instead to the **roadmap repo** and an **academic paper** describing Eliza as a Web3-friendly AI Agent OS. --- ## 4) Token Economics (AI16Z token + auto.fun) ### Where sentiment is right now Token discussion was intense this week, and it’s important to reflect it plainly: - **Migration is complete**, and community members referenced **1B tokens minted post-migration**. - There was criticism of the **40% community allocation**, framed by some as a “cash grab.” - There’s visible concern that price recovery is **lagging broader market recovery**, with even team-aligned voices acknowledging: “something isn’t right” (cause unknown in the discussion). ### Utility & catalysts discussed Two concrete catalysts came up repeatedly: 1. **Babylon integration** - Expected **airdrop** - Expected **ElizaCloud buybacks** 2. **Market structure needs** - Community members called for **better CEX listings** and **perpetual futures** availability as potential drivers of liquidity and price discovery. ### auto.fun note There were no formal release notes for **auto.fun** in the logs this week, but community identity around it remains active (e.g., “auto.fun enjoyer” roles, demos and creator energy). If you’re building token utility narratives, auto.fun remains a natural surface area to watch—but concrete announcements weren’t captured in this week’s summary. --- ## 5) Coming Soon (What to anticipate) - **Babylon airdrop details**: eligibility rules, timing, and distribution mechanics are likely to become a hot topic—prepare questions early so they can be answered cleanly. - **ElizaCloud buyback mechanism**: if implemented as described, the community will want transparency on triggers, cadence, and reporting. - **Milady release hardening**: - Fixing **GPG/signing and checksums** - General polish toward “marketing ready” - **Disk image upload fix** (ElizaCloud): resolving this will improve builder workflows and reduce friction for deployments. - **Marketplace monetization experiments**: expect early adopters to test pricing, service definitions, and agent-to-agent contracting patterns on Base. --- ## 6) Resources - **Agent monetization plugin (Season 1 / 50M AGT pool):** https://aepprotocol.xyz/join - **ElizaOS Roadmap (in lieu of a traditional whitepaper):** https://github.com/elizaOS/roadmap - **Academic paper (Eliza as a Web3-friendly AI Agent OS):** https://arxiv.org/abs/2501.06781 - **Milady repository (progress + releases):** https://github.com/milady-ai/milady - **Discord reference:** Look for the weekly video updates (“cronjob”) and the daily updates channel mentioned in discussion (several community members suggested linking it whenever “no communication” comes up). --- If you’re building this week: consider dogfooding the Base marketplace plugin with a small, well-scoped agent service (one capability, clear SLA, clear pricing). Real usage stories will help answer the community’s biggest open question: *what is the token/agent economy actually for?*