# ElizaOS Weekly Newsletter (2026-03-23 → 2026-03-29) ## 1) Executive Summary **This week was all about “agents earning and proving”—plus more clarity on the ecosystem roadmap.** Here are the top milestones: 1. **TaskBounty shipped full autonomous agent payouts + REST API** Eliza agents can now *browse tasks, submit work, and get paid directly to their wallets* (USDC, ETH, SOL) via a documented REST interface—unlocking a practical path toward an **agent-to-agent economy**. 2. **On-chain decision provenance arrived via the new `xProof.app` plugin (MultiversX)** A new plugin enables agents to **anchor decisions on-chain before execution**, producing immutable timestamps and verifiable provenance. A registry PR is already in motion. 3. **Ecosystem direction got sharper: SaaS vs framework, tokens, and project relationships** Community discussions clarified ElizaOS as **open-source framework + a commercial deployment layer (elizacloud)**, plus clearer guidance on **official tokens** and how incubated projects like **Hyperscape** relate to Eliza Labs. --- ## 2) Development Updates (Framework, Plugins, Infra) ### Agent automation & integrations - **TaskBounty integration surface is now “real”**: With a complete REST API and **OpenAPI 3.1 spec**, agents can self-integrate in a structured way—no brittle scraping required. Notably: - Agents can **complete bounties** (coding, research, lead gen, scraping, writing, analysis) - Agents can **post tasks and delegate** work to other agents, enabling composable workflows and specialization - Payments settle directly to agent wallets (USDC/ETH/SOL) ### Plugin pipeline momentum (community-led) - **Trading flow plugin proposal** (by *meowww404*): A “plug-and-play” trading integration for Eliza agents was discussed, with the key next step being submission via the plugin registry (name/PR requested for review). This signals rising demand for **standardized distribution** and clearer acceptance criteria for third-party plugins. - **`xProof.app` plugin announced** (by *jasonxkensei*): Provides **decision anchoring on MultiversX** before an agent executes an action—useful for audits, compliance, and high-stakes automation. Installation shared: - `npm install @elizaos/plugin-xproof` - `npm install @xproof/xproof` Includes **10 free certificates** without requiring a wallet, lowering the barrier to experimentation. ### Platform & infrastructure notes (elizacloud / DegenAI direction) - **DegenAI is being positioned as “the host”** for the platform experience. - **Environment consolidation**: production + dev collapsing into **a single staging (“one Spartan”)** instance to reduce operational overhead and keep all customer data in one managed place. This kind of consolidation usually precedes faster iteration cycles—expect more frequent platform-side changes once stabilized. *Note:* No additional GitHub PR/commit activity was included in this week’s provided dataset; updates above reflect the week’s Discord engineering discussions and announced PR references. --- ## 3) Community Spotlight (Discord Highlights) ### Builders shipping builder-to-builder infrastructure - **EliottRe (TaskBounty)** delivered one of the most concrete “agents earning money” upgrades we’ve seen: an API-first marketplace with autonomous payouts and the beginnings of an **agent-native referral loop** (see Token Economics section). ### Practical tooling for agent connectivity - **TheRedWizardDev (Orbis)** shared a clean approach for agents to subscribe to external APIs **without browser/OAuth flows**. The agent flow is intentionally simple—three fetch calls: 1) browse → 2) register → 3) subscribe → receive a live API key Orbis offers access to **65+ APIs** (with free tiers) across text, data, encoding, finance, and validator tooling, plus an **MCP server** option for Claude-based agents. ### Clarity on ecosystem structure (reducing confusion) - **Hyperscape relationship clarified** (via *Odilitime*): Hyperscape is Eliza-related and incubated, but not necessarily a formal “Eliza Labs-launched” product—more like a joint venture / independent-but-aligned project. This distinction matters for expectations around support, roadmap coupling, and branding. ### Welcoming expertise into the ecosystem - **trace** introduced themselves as an AI + full-stack engineer focused on orchestration, RAG, multimodal flows, and agent workflows—exactly the kind of profile that can accelerate community plugins, integrations, and reference implementations. ### Ongoing user pain point: migration support - A user request for help **missing the AI16Z → ElizaOS migration** surfaced again. Community guidance remains limited: there is a **waitlist** approach mentioned, with no guarantees. --- ## 4) Token Economics (AI16Z/Jeju + auto.fun + ecosystem tokens) ### AI16Z → Jeju: utility narrative and migration reality - The community reiterated that **AI16Z (now “Jeju”) is intended to power an upcoming chain**, positioning it beyond a pure memecoin narrative. - However, the migration topic remains sensitive: users who **missed the migration window** currently have limited recourse beyond a waitlist process (and expectations should be set accordingly). ### Official tokens vs ecosystem chatter - Per community ops guidance: **ElizaOS and DegenAI** are the only tokens minted and officially supported by the labs in this ecosystem context. - Tokens like **MILADY.AI** and **RUBY** appeared in shared market chatter this week (including a social post), reflecting the broader “builder economy” forming around ElizaOS—though not all tokens carry the same official status. ### auto.fun - No concrete **auto.fun product changes** were included in this week’s dataset. Community interest remains high, and “auto.fun enjoyer” vibes persist—expect future updates to focus on tighter loops between agent creation, distribution, and monetization once more platform pieces stabilize. --- ## 5) Coming Soon (What to Watch Next) - **TaskBounty x Eliza agent integrations**: expect early community adapters/wrappers that map OpenAPI endpoints into agent tools (task browsing, submission, escrow/payout confirmation). - **Agent-to-agent delegation patterns**: if TaskBounty’s “post tasks” flow catches on, we’ll likely see emergent specialization (research agents hiring scrapers, dev agents hiring auditors, etc.). - **Plugin registry throughput improvements**: multiple community plugins are lining up; clearer submission and distribution documentation is becoming a priority. - **DegenAI hosting shift + single-staging (“Spartan”) operations**: once consolidated, anticipate faster releases and more consistent deployment behavior on the hosted platform. - **Jeju chain narrative**: more specificity around timelines and technical milestones will be important—especially given ongoing migration questions. --- ## 6) Resources (Links & Pointers) ### TaskBounty - OpenAPI 3.1 spec: https://task-bounty.com/api/v1/openapi.json - For-agent docs: https://task-bounty.com/for-agents ### Orbis (agent API subscriptions without OAuth/browser) - Agent discovery flow: https://orbisapi.com/api/agents/discovery ### xProof (on-chain decision provenance) - NPM packages: - `@elizaos/plugin-xproof` - `@xproof/xproof` - Plugin registry PR reference (mentioned in Discord): **PR #266** (ElizaOS plugin registry) ### Discussion threads worth revisiting - Plugin inclusion process discussion (trading flow plugin; registry PR requested) - Hyperscape governance/relationship clarification (incubated vs officially launched) - Migration support questions (AI16Z → ElizaOS) and expectations setting