## Weekly Newsletter (2026-03-20 → 2026-03-26) ### 1) Executive Summary **1) Nosana × ElizaOS partnership kicked off the “Nosana Builders’ Challenge.”** This week brought a concrete builder-focused milestone: Denis announced a partnership between Nosana and ElizaOS, with the **Builders’ Challenge launching March 25** and **workshops scheduled for March 26 and April 2**. The goal is simple: get more agents shipped, faster—plus direct support for participants who get stuck. **2) On-chain market intelligence got easier with the release of the Pythia MCP server.** Ivan Jeremic shared the **Pythia MCP server**, enabling agents to query **verifiable on-chain market indicators** (via Chainlink oracles on Polygon) across **13 tokens** and **4 timeframes**, including **EMA, RSI, VWAP, Bollinger Bands, and volatility metrics**—notably **without API keys**. This is a meaningful step toward robust DeFi/trading agents that can operate without brittle off-chain dependencies. **3) Autonomous trading agents and “agent personalization” moved to the center of community building.** Multiple threads converged on autonomous trading: from builders explicitly asking for review of their setups, to a standout community project (“The Undesirables”) that deterministically maps **NFT traits → agent personality** and packages each NFT as an ElizaOS-compatible workspace with a **MemGPT-style memory stack** and live market data injection. --- ### 2) Development Updates (Technical) **Autonomous trading agent patterns: the community is aligning on the building blocks.** Across the week’s Discord conversations, there’s an emerging “standard kit” for trading agents on ElizaOS: - **Reliable market context** (live feeds or on-chain oracles) - **Memory that supports long-running behavior** (multi-tier memory / summaries / recall) - **Personality + policy constraints** (risk appetite, reactivity, “style,” and guardrails) - **Reproducible configuration** (shareable specs, portable character definitions) While we don’t have a new GitHub PR/commit batch included in this week’s aggregated data, Discord made it clear that builders are actively pushing these patterns into real deployments. **Pythia MCP server: “no API keys” market indicators via Chainlink on Polygon.** Ivan’s release is especially relevant for anyone building autonomous or semi-autonomous DeFi agents. Key details shared: - Uses **Chainlink oracles on Polygon** - Covers **13 tokens**, **4 timeframes** - Provides indicator suite: **EMA, RSI, VWAP, Bollinger Bands, volatility** - Install path mentioned: `pip install pythia-oracle-mcp` - Benefit: **removes API-key ops burden** and reduces reliance on off-chain data pipelines If you’re building agents that need to justify decisions with verifiable inputs, this is a strong foundation. **Security note: supply chain risk surfaced (litellm-pypi attack).** DorianD flagged a **supply chain attack on `litellm-pypi`**, with Odilitime acknowledging it. Even if your agent is “just a bot,” dependency integrity is now a first-class operational concern—especially for agents with wallets, execution permissions, or deployment keys. **Milady app status: still actively being built, no date yet.** Odilitime confirmed ongoing work (including weekend dev time). Community asked repeatedly about timelines; the consistent message remains: **launch when ready**. --- ### 3) Community Spotlight (Discord) **sailorpepe.eth — “The Undesirables”: 4,444 NFT workspaces as ElizaOS-compatible agents** One of the most technically detailed community shares this week: a system where each NFT’s visual traits deterministically generate a personality across **7 dimensions** (Big Five + trading scores). Notable architecture pieces: - **ElizaOS V1 spec compatibility** - YAML frontmatter - `character.json` export - **3-tier MemGPT-style memory architecture** - **Live market data pipeline** injecting context directly into sessions - CoinGecko, DeFiLlama, DexScreener APIs - A “soul viewer” interface and downloadable workspaces This is a real example of *packaging agents as portable products*, not just prompts. **Ivan Jeremic — Pythia MCP server release and integration offer** Ivan didn’t just drop a tool—he offered integration help and explained the core value proposition clearly: verifiable indicators, fewer secrets to manage, and less fragile infrastructure. **Denis — Builder enablement through the Nosana Builders’ Challenge** Denis’s presence was practical and builder-centric: clear schedule, clear offer of support, and a clear “ship and learn” loop via workshops. **Ape Ape | KairoGuard — call for collaboration on autonomous trading setups** Ape Ape asked directly: *who’s actually running autonomous trading agents on ElizaOS, and can someone review my setup?* Denis suggested the hackathon as a proving ground, and gelgit.eth requested to see the setup. If you’re building in this space, this is exactly the kind of peer-review thread that helps the whole ecosystem mature faster. --- ### 4) Token Economics (AI16z token + auto.fun + broader token chatter) **No official AI16z token or auto.fun product updates were included in this week’s aggregated data.** So, we’re keeping this section grounded: **no confirmed launches, parameter changes, or treasury/mechanism updates** were captured in the provided sources for this period. **What did show up: community demand for clearer token/platform messaging.** - Questions were raised about the relationship between **“base Milady” vs “SOL milady.ai”** tokens and whether the **Milady app supports both**. This went unanswered in the captured discussion, which is a signal: **documentation clarification is needed** to reduce confusion (and risk) for new users. **Market sentiment and morale:** There were candid conversations about token price action (including pessimistic takes and pattern speculation). Rainman encouraged the community to focus on official updates and the broader thesis that **2026 will be a major year for agentic AI**. *Takeaway:* the community is hungry for **clear, canonical token references** (which contract, which chain, what the app supports) and for **official “source of truth” links** that can be shared with newcomers. --- ### 5) Coming Soon **Nosana Builders’ Challenge workshops** - **March 26** workshop (today) - **April 2** follow-up workshop If you’ve been waiting for a structured moment to ship an agent, this is it—especially for trading/DeFi agent experiments. **More autonomous trading agent sharing + review** - Ape Ape’s request for feedback is a good template: share architecture, constraints, evaluation approach, and failure modes. - Expect more builders to converge on reusable patterns (memory, data, execution safety). **Security hardening discussions** - The `litellm-pypi` incident should trigger routine practices: dependency pinning, SBOMs, lockfile hygiene, and “wallet-separated” execution environments for agent runners. **Milady app** - Still in development; community should anticipate iterative updates rather than a fixed-date promise. --- ### 6) Resources (links & pointers) - **Discord: General discussion (introductions + token/app questions)** https://discord.com/channels/1253563208833433701/1253563209462448241 - **Discord: Coders channel (trading agents + The Undesirables share)** https://discord.com/channels/1253563208833433701/1300025221834739744 - **The Undesirables (project link shared in Discord)** https://the-undesirables.com/ - **Pythia MCP server (install mentioned in Discord)** `pip install pythia-oracle-mcp` (If you adopt it, consider posting a short integration note in #coders so others can replicate.) - **Security reference (discussion: litellm-pypi supply chain attack)** Captured in Discord on 2026-03-24; if you rely on LiteLLM or similar tooling, audit your dependency tree and pins. ---