## Weekly Newsletter (2026-03-21 → 2026-03-27)

### 1) Executive Summary

**A big week for “agents + on-chain” momentum across the ecosystem.** Here are the main wins:

1. **Nosana × ElizaOS partnership kicked off the Nosana Builders’ Challenge (launching Mar 25)**, including hands-on workshops (Mar 26 and Apr 2) and direct support for builders who get stuck.
2. **Two major “trust + data” building blocks landed in the community spotlight:**
   - **xProof.app**: an ElizaOS plugin for **on-chain decision provenance** (anchors agent decisions on MultiversX before execution).
   - **Pythia MCP server**: a tool for agents to query **verifiable on-chain market indicators** via Chainlink oracles on Polygon—no API keys, no off-chain pipelines.
3. **Platform direction got clearer**: Odilitime reiterated ElizaOS as an **open-source framework** plus a commercial **SaaS deployment layer (elizacloud)**, while development continues toward **DegenAI as the hosting “face”** of the platform and infrastructure consolidation to simplify operations.

---

### 2) Development Updates (Framework, Plugins, Infra, Security)

#### **On-chain decision provenance: xProof.app plugin (MultiversX)**
A new plugin announcement stood out for teams building agents that need auditable behavior:

- **What it does:** “Anchors every agent decision on MultiversX before execution,” producing **immutable timestamps** generated by the chain (not by the agent).
- **Why it matters:** This is a practical step toward **verifiable agent operations**—useful for trading agents, governance agents, or any workflow where you want tamper-evident logs and external verification.
- **How to install:**
  - `npm install @elizaos/plugin-xproof`
  - `npm install @xproof/xproof`
- **Cost/UX note:** Includes **10 free certificates** and **does not require a wallet** to get started.
- **Registry status:** A PR is open to add it to the official plugin registry (**PR #266**).

#### **Verifiable market data for agents: Pythia MCP server**
Ivan Jeremic released the **Pythia MCP server**, aimed squarely at DeFi and trading use cases:

- **Data source:** Chainlink oracles on **Polygon**
- **Coverage:** 13 tokens × 4 timeframes
- **Indicators:** EMA, RSI, VWAP, Bollinger Bands, and volatility metrics
- **Key advantage:** Eliminates the need for API keys and centralized data vendors; agents can query **on-chain indicators** directly.
- **Install:** `pip install pythia-oracle-mcp`

This pairs nicely with the community’s ongoing interest in autonomous trading agents: one tool for **reliable signals**, another for **decision auditability**.

#### **Infrastructure consolidation: “one Spartan” staging**
Odilitime shared an operational change in-flight:

- Production and development environments are being **collapsed into a single staging environment**, creating **one Spartan instance** to manage (with all customer data).
- The goal is simpler deployments and fewer moving parts while the hosted experience matures.

#### **Security heads-up: supply chain risk**
A community alert flagged a **supply chain attack on `litellm-pypi`**. No remediation steps were documented in-chat this week, but it’s a strong reminder to:
- pin dependency versions,
- audit transitive dependencies,
- and review CI/CD package integrity (especially for agent runtimes that can touch keys, wallets, or trading endpoints).

---

### 3) Community Spotlight (Notable Contributions + Discord Discussions)

#### **Autonomous trading agents: builders looking for peer review**
Discussion repeatedly returned to **autonomous trading agents on ElizaOS**. Ape Ape | KairoGuard asked for feedback and collaboration on their setup, and Denis suggested using the newly launched builder challenge/hackathon environment to test ideas and get iteration cycles going quickly. If you’re running live strategies, consider sharing:
- execution constraints (slippage, rate limits, chain selection),
- safety rails (max position sizing, kill switches),
- and evaluation methodology (paper trading vs. small-size mainnet trials).

#### **NFT-based agent workspaces with deterministic personalities (4,444 agents)**
sailorpepe.eth showcased a substantial build: an NFT collection mapped to **4,444 unique AI agent workspaces**, where visual traits deterministically generate personality across **7 dimensions** (Big Five + trading scores).

Notable technical pieces:
- **ElizaOS V1 spec compatibility** (YAML frontmatter + `character.json` export)
- **3-tier MemGPT-style memory architecture**
- **Live market data pipeline** integrating CoinGecko, DeFiLlama, DexScreener directly into sessions
- A “soul viewer” interface plus downloadable workspaces

Even if you’re not in NFTs, the deterministic “traits → behavior config” pipeline is a useful pattern for anyone shipping **agent personalization at scale**.

#### **Hosting options expand: hatcher.host**
HatcherLabs introduced **hatcher.host**, offering hosting for **ElizaOS and Milady deployments** with a free trial and a request for community feedback. This is a positive signal: more hosting providers usually means faster onboarding, clearer pricing pressure, and more deployment templates for newcomers.

#### **Ecosystem clarity: framework vs. platform**
Odilitime repeatedly clarified the structure:
- **ElizaOS = open-source framework**
- **elizacloud = commercial SaaS** to make deploying agents easier
- Multiple ecosystem projects are building on the framework, including **Babylon**, **Hyperscape**, and **Milady** (with an explicit goal of enabling agents to play Hyperscape via elizacloud).

---

### 4) Token Economics (AI16Z/Jeju + auto.fun)

#### **AI16Z → Jeju: utility narrative + migration reality**
Odilitime reiterated that **AI16Z (now “Jeju”) is intended to power an upcoming chain**, positioning it beyond memecoin-only narratives.

However, an important operational note remains: **holders who missed the migration window currently have limited recourse**. A waitlist exists via DM, but **no guarantees** were offered.

#### **BitDelta exchange listing offer**
ruby_bitdeltalisting shared that **BitDelta offered a free listing** for AI16Z/Jeju after internal due diligence and is looking to coordinate with **marketing/growth** for rollout planning. If you’re plugged into growth efforts, this is a tangible opportunity to help with:
- announcement timing,
- liquidity planning,
- messaging consistency (Jeju chain utility, migration clarity, risk disclaimers).

#### **auto.fun**
No concrete product updates were captured in the provided logs for auto.fun this week. If there were launches or parameter changes, share links in Discord and we’ll include them in next week’s roundup.

---

### 5) Coming Soon (What to Watch Next)

- **Nosana Builders’ Challenge momentum** continues, with another workshop scheduled for **Apr 2**.
- **Plugin registry addition for xProof** (pending review/merge of PR #266). If accepted, expect broader adoption for compliance-minded or trust-minimized agent deployments.
- **DegenAI hosting roadmap**: continued progress toward making DegenAI the platform host, plus the operational shift to a single staging environment.
- **Babylon integrations**: DegenAI is expected to support **prediction market functionality** and **autonomous trading** in Babylon contexts.
- **Jeju chain**: community continues to frame Jeju as future chain power; watch for concrete launch artifacts and technical docs.

---

### 6) Resources (Links & Pointers)

- **Nosana × ElizaOS Builders’ Challenge announcement (Discord context):**  
  https://discord.com/channels/1253563208833433701/1253563209462448241
- **xProof plugin install info (Discord coders channel context):**  
  https://discord.com/channels/1253563208833433701/1300025221834739744  
  - npm: `@elizaos/plugin-xproof`, `@xproof/xproof`  
  - Registry PR: **elizaos-plugins/registry PR #266**
- **Pythia MCP server (on-chain indicators via Chainlink on Polygon):**  
  Install: `pip install pythia-oracle-mcp`
- **BitDelta listing coordination thread (Discord discussion context):**  
  https://discord.com/channels/1253563208833433701/1253563209462448241
- **Security note (dependency supply chain awareness):**  
  Track the `litellm-pypi` incident and review your agent runtime dependencies accordingly.

---