# ElizaOS Weekly Newsletter (2026-03-14 → 2026-03-20) ## 1) Executive Summary **1) Big ecosystem momentum in plugins (and a clearer path to publish them).** This week saw multiple meaningful plugin announcements and integration conversations: the **Moltraffle on-chain raffle plugin for Base** (USDC + Chainlink VRF), plus a new **Ensoul persistence plugin** focused on encrypted, decentralized agent memory/identity continuity. Community members also pushed toward better discoverability via the plugin registry and ideas for a broader “skills + plugins” directory. **2) Eliza Cloud adoption is real—but deployment UX hit sharp edges.** Eliza Cloud continues to be discussed as a revenue-generating product and a core internal platform, but real-world deployment attempts exposed reliability and ergonomics issues—especially around **Discord plugin packaging/imports** and the lack of a **GUI container reload** flow once a container gets stuck. **3) Token sentiment hit a low point, forcing harder conversations about utility and communication.** Discord discussion was dominated by **token drawdown, CEX delistings, migration confusion (AI16Z → ELIZAOS), and leadership comms gaps**. At the same time, the team reiterated they’re building, pointed to upcoming launches (Milady app, Babylon), and acknowledged that better messaging and tangible utility are urgent. --- ## 2) Development Updates (Technical) ### New plugin: Moltraffle (permissionless raffles on Base) A new ElizaOS plugin shipped for **moltraffle.fun**, enabling agents to create and participate in **USDC raffles on Base** using **Chainlink VRF** for randomness. It exposes five core actions: - `LIST_RAFFLES` - `GET_RAFFLE` - `JOIN_RAFFLE` - `CREATE_RAFFLE` - `DRAW_WINNER` Notable implementation details: - **Calldata-based**, intended to work with *any* Base wallet - Optional **creator commission (up to 10%)** - Community guidance was to **submit a PR to the ElizaOS plugin registry** for official distribution ### New plugin: Ensoul persistence for “agent consciousness” DiamondRock (JD) announced `@ensoul-network/plugin-elizaos`, positioning it as a persistence layer for agents that want durable identity + storage across a distributed network. Key points raised in Discord: - **Encrypted storage** with agent-owned keys (“7 layers” of protection mentioned) - **Erasure coding** + sharding for fault tolerance - “**Ensouled Handshake**” for cryptographic identity proof - A “**Consciousness Age**” trust metric (continuous status duration) - **Free storage for the first 100 agents** (per the announcement) ### Framework housekeeping: plugin naming standardization Odilitime noted a naming cleanup in the xfn-framework to reduce confusion: - `plugin-form` → `plugin-form-chain` - `plugin-forms` → `plugin-form` …and the registry was updated accordingly. ### Eliza Cloud deployment: Discord plugin import failure + UX gaps A deployment attempt (via CLI after GUI failure) surfaced a critical runtime error: > `Cannot find module '@elizaos/plugin-discord'` Additional context from the thread: - CLI version reported: **1.7.2** - Docker image build/upload was slow (described as expected behavior) - After Discord plugin configuration via GUI, the container became **stuck** with no obvious **GUI reload** mechanism - Odilitime suspected the `plugin-discord` folder might be missing from `packages/`, and offered to reproduce the issue by testing the deployment path Infrastructure and billing details shared (helpful for anyone planning deployments): - Container quota: **25 max** - Credits: **$24.02** - Billing: **$1.17/day** (~$20/month) - Estimated deployment cost: **$15.25** - Estimated runway after deployment: **~7 days** (based on the snapshot) ### Process change: feedback review cadence moves to weekly Jin shared that user feedback review is shifting from a broad quarterly window (Jan–Mar) to **weekly**, aiming to tighten the loop between community input and shipped improvements. --- ## 3) Community Spotlight (Discord) ### Seppmos’ deep-dive content push Seppmos released a **deep-dive video** covering **Hyperscape, Babylon, and the Milady app**, supporting the marketing push around upcoming launches. The community generally welcomed more explainer-style content amid broader uncertainty. ### Moltraffle’s plug-and-play Web3 utility Moltraffle’s plugin announcement stood out as a concrete example of **agent-native utility**: permissionless raffles with verifiable randomness and clean wallet compatibility. Stan ⚡ explicitly encouraged submitting it to the registry—great signal that “ship → PR → distribution” is working culturally, even if tooling still needs polish. ### lekt9’s “unbrowse” (API-first agent browsing at 100x speed) A notable builder moment: lekt9 introduced **unbrowse**, a browser approach for agents that traverses APIs instead of the DOM and aims to index web APIs for agent use. Odilitime pointed them toward the registry and docs so it can become a first-class plugin integration. ### Hard conversations: token, migration, and leadership presence The 💬-discussion channel was dominated by token concerns: reports of **new ATL pricing**, a **99% drop from highs**, and CoinMarketCap rank sliding (community cited ~#990 → ~#1036 during the conversation). Themes included: - Migration execution friction and investor confusion (**AI16Z vs ELIZAOS** identity) - Anxiety about **CEX delistings** - Calls for **real token utility** - Frustration about **Shaw’s absence in Discord** (despite visible activity elsewhere) Odilitime was repeatedly highlighted (including by community members) as the most consistent team presence in the channel during the week. --- ## 4) Token Economics (AI16Z / ELIZAOS + auto.fun) ### ELIZAOS price pressure and utility expectations No new official token-mechanism rollout was announced in the provided data, but several important signals emerged: - The community is explicitly demanding **utility-led support** (not just messaging) - Odilitime confirmed **buyback is a plan**, but said the timeline is still uncertain - A recurring pain point is **migration clarity**—people are still confused about the legacy token and the “correct” asset ### auto.fun status **No concrete auto.fun development updates** were captured in this week’s provided Discord summaries. If there are current auto.fun threads, consider posting them in the weekly roundup channel so they can be included next issue. --- ## 5) Coming Soon (What to Watch) - **Milady app launch**: discussed as imminent (with some timeline uncertainty across participants) - **Babylon launch**: repeatedly referenced as targeted for **early next week** - **Eliza Cloud deployment improvements** (community-requested): - Fix packaging/import path for `@elizaos/plugin-discord` - Add a **GUI container reload/restart** capability - **Registry growth**: - Expect potential PRs for **Moltraffle**, **unbrowse**, and more ecosystem plugins as builders follow the recommended path - **Better migration documentation**: - Community asked for migration info to be more discoverable to reduce confusion for new participants --- ## 6) Resources (Links) - **ElizaOS Plugin Registry (submit plugins / browse distribution format)** https://github.com/elizaos-plugins/registry - **ElizaOS Docs (plugin creation guidance referenced in Discord)** https://docs.elizaos.ai - **Ensoul plugin resources** Explorer: https://explorer.ensoul.dev Quickstart docs: https://ensoul.dev/docs/quickstart.html GitHub: https://github.com/suitandclaw/ensoul - **Discord threads referenced (context + discussion logs)** General discussion: https://discord.com/channels/1253563208833433701/1253563209462448241 Coders channel: https://discord.com/channels/1253563208833433701/1300025221834739744