## Weekly Newsletter (2026-02-23) — Week of **2026-02-16** to **2026-02-22** ### 1) Executive Summary **A big NFT utility announcement landed for elizaOS holders.** Milady revealed **AGENTS**, an ERC-8004 NFT drop (using the **ERC-8041 fixed agent collection** standard) with **free minting** and **upgraded mints for elizaOS holders** across multiple chains. It’s a meaningful “ecosystem utility” moment: on-chain collectibles tied directly to the agent stack and community identity. **Core devs pushed forward on the v2 database refactor path.** The standout was **PR #6521**, which removes ~2,600 lines by dropping legacy auto-migration code (1.4.x → 1.6.x) and tightens the isolation story (RLS) in a way that’s easier to reason about for v2.0.0 going forward. **The plugin ecosystem kept expanding—this time into autonomous BD.** SolCex Exchange shipped a **v2.0.0 plugin** that acts like a business development agent for exchange listings, with scoring + multi-source intelligence. It’s a good example of what “agents as specialized operators” looks like in practice. --- ### 2) Development Updates (Core + Tooling) #### Database refactor & migration strategy (v2.0.0) Work this week converged on simplifying the database layer and clarifying upgrade expectations: - **PR #6521 (plugin-sql / isolation refactor):** - Removes approximately **2,600 lines**—mainly the **auto-migration path from 1.4.x to 1.6.x**. - Migration strategy is now more explicit: if you’re *still* on 1.4.x, the likely path will be **upgrade to 1.6.x first**, then move to v2.0.0. (A future improvement discussed: fail fast with a helpful error that enforces this path.) - Improves RLS / isolation patterns: replaces `application_name`-based server context with **parameterized `set_config`** calls for stronger **SQL injection safety**. - Renames `withEntityContext` → **`withIsolationContext`** to better match the intent. This aligns with the broader direction: v2.0.0 is the “future branch,” even if docs are still catching up. #### Performance & prompt budget pressure Odilitime called out a recurring real-world scaling pain: **hitting ~200k token limits** when many plugins are active. The suspected major contributors: - **Bootstrap providers** - **Evaluations** The team is actively working on reducing baseline prompt bloat and improving efficiency (this pairs nicely with recently introduced relevance filtering ideas like action/provider filtering—more on that in “Coming Soon”). #### Cloud & dashboard issues (ElizaCloud) Community testing surfaced UX and API issues that were forwarded to the team: - Broken mousepad scrolling on the API explorer page; scrollbar is hard to discover. - “Send request” failing with **“api key is required”** even when an API key appears present. - Requests for clearer **BYOK (“use a different key”) behavior** and a per-model pricing breakdown. #### Docs & maintenance - A new **Base Network wallet safety guide** was proposed (including **x402 diagnostic** guidance). - Routine dependency updates landed (npm/yarn group bumps). --- ### 3) Community Spotlight (Discord) **DarmaStef’s agent builder showcase** was a highlight: they shared examples of building practical agents (Reservation Agent, Travel Agent, Database Analysis Agent) specifically aimed at **non-technical users**, and offered to collaborate with others. This kind of “here’s what I built, and here’s how it helps normal people” is exactly the energy that makes the ecosystem legible beyond the core dev circle. **Project positioning got clarified—again, in a healthy way.** Odilitime reiterated that elizaOS is about **democratizing agent capability**, not pitching short-term profit. The community also revisited the historical **ai16z → elizaOS migration** (1:6 ratio; with 1:4 allocated for funding), and the practical reality that **ai16z is effectively deprecated** with liquidity and development attention under elizaOS. **Interesting technical threads worth noting:** - **“Unbreakable agents” via Erlang**: King Nebuluz shared progress and code for potential integration. - A weird-but-real bug report: an openclaw agent unexpectedly responding in **Korean**, likely a configuration/localization edge case worth triage. **Small but important:** branding consistency—“**elizaOS**” capitalization was reinforced (it matters for docs, searchability, and ecosystem coherence). --- ### 4) Token Economics (AI16z token + auto.fun + ecosystem utility) #### elizaOS holder benefit: Milady AGENTS NFT drop Milady announced **AGENTS**, an ERC-8004 NFT collection with: - **2138 NFTs per chain** across **ETH, BSC, Base, and Solana** - **Free mint** - **Upgraded mints** for **OG Milady**, **Remilio**, and **elizaOS holders** across all chains - Availability through the **Milady app** There was some community confusion about *which token* the “upgrade” applied to (milady.ai vs elizaOS), but the working understanding in Discord is that **elizaOS holders are included in the upgrade path**. Also important: **milady.ai token is not launched yet**, which explains why people couldn’t find it in Phantom. #### AI16z status From community Q&A: **ai16z is considered deprecated** in practice; the ecosystem is now multi-chain under the elizaOS umbrella. #### auto.fun This week’s data referenced lingering community sensitivity after recent **Autofun/Twitter incidents**, but there were **no concrete shipped auto.fun product changes** captured in the logs. If you’re tracking auto.fun closely, keep an eye on official channels (Twitter for AI/dev; Farcaster for crypto updates). --- ### 5) Coming Soon - **Cleaner v2 upgrade UX:** likely guardrails that prevent “1.4.x → v2.0.0” direct upgrades, with explicit instructions to migrate via **1.6.x** first. - **NFT capability expansion via plugin-evm:** Odilitime confirmed ongoing work to unlock broader NFT functionality; community even floated the idea of an “**elizaOK**” NFT concept. - **Prompt/pipeline efficiency improvements:** expect continued reductions in token usage driven by bootstrap/evaluation optimization—especially important for plugin-heavy agent builds. - **Registry growth:** pending review/merge of **SolCex plugin registry PR #263**, plus related ecosystem additions (SAID identity tooling remains a major theme in recent PRs). --- ### 6) Resources (Links & Pointers) **Discord threads** - Partners channel (token holder upgrade + milady.ai launch status): https://discord.com/channels/1253563208833433701/1301363808421543988 - Coders channel (SolCex plugin + RSS): https://discord.com/channels/1253563208833433701/1300025221834739744 - Core devs (DB refactor / PR #6521 discussion): https://discord.com/channels/1253563208833433701/1377726087789940836 - General discussion (agents showcase + ecosystem Q&A): https://discord.com/channels/1253563208833433701/1253563209462448241 **GitHub / engineering** - DB isolation + migration cleanup: **elizaos/eliza PR #6521** (discussed in core-devs) - Base wallet safety guide with x402 diagnostics: **elizaos/eliza PR #6523** - Plugin registry submission: **elizaos-plugins/registry PR #263** (SolCex BD plugin) **News / updates** - elizaOS.news RSS feed: https://elizaos.news/rss/feed.xml If you built something cool this week—an agent, a plugin, even a reproducible bug report—drop it in Discord. The fastest improvements lately are coming from builders sharing concrete artifacts the rest of the community can test and extend.