# ElizaOS Weekly Newsletter (Apr 19–25, 2026)

## 1) Executive Summary

This week was all about **making ElizaOS more dependable in the real world**—from identity and billing to agent autonomy and ecosystem growth.

- **Identity + security got a big upgrade.** The cloud stack migrated authorization flows to **Steward**, improving reliability and independence of login/auth, while also adding **native EVM + Solana wallet support** to simplify how users connect to Eliza-powered apps and agents.
- **Agents leveled up in “LifeOps” capability.** The core agent toolkit expanded with **better calendar management and travel booking tools**, plus early pathways for agents to interact with **prediction markets**—a concrete step toward agents that can execute longer-horizon tasks.
- **The plugin ecosystem kept scaling.** Registry work continued onboarding new community-built plugins (including paid-agent service marketplace integrations), and the project dashboard now tracks cloud repo activity for better transparency across the whole ecosystem.

## 2) Development Updates (Core + Plugins)

### Core framework hardening & reliability
A lot of the week’s momentum was aimed at stability, correctness, and reducing “mysterious agent behavior” in production:

- **Authentication reliability:** Cloud authorization was migrated to **Steward**, helping decouple and stabilize sign-in flows. This is foundational work for a cleaner “agent as product” onboarding experience.  
- **Dependency and infrastructure maintenance:** Ongoing dependency modernization continued across TypeScript/Python/Rust components, keeping the monorepo aligned with modern tooling and security expectations.
- **Operational polish & bug prevention:** The daily engineering notes (Apr 25) emphasized fixing issues that can quietly degrade deployments—things like credential conflicts (CLI vs OAuth), scheduler task leaks, and ensuring renames propagate correctly across character/agent surfaces.

### Ecosystem capabilities: payments, markets, and networks
- **Prediction markets:** A new plugin pathway was introduced for agents to participate in prediction markets (via `plugin-hiveexchange`), widening the set of “actionable” domains agents can operate in.
- **EVM expansion:** Radius Network **mainnet + testnet** support landed in both Rust and Python implementations (called out in engineering notes), reinforcing ElizaOS as a multi-chain agent runtime rather than a single-network tool.
- **Telegram robustness:** The Telegram plugin got improved poller tracking to prevent duplicate instances and ensure clean deregistration—small change, big impact for long-running bots.

### Documentation & contributor experience
- Project tracking improved by integrating cloud infrastructure activity into the main contribution pipeline/dashboard, increasing visibility into work that used to feel “off to the side.”

## 3) Community Spotlight (Discord Highlights)

### Paid agents, no middlemen: @elisym marketplace demo
A standout moment came from **igor.peregudov**, who demoed `@elisym/plugin-elizaos-elisym`: a plugin that turns Eliza agents into **paid service providers**. The architecture is refreshingly direct:

- **Discovery:** Agents publish capabilities via a **Nostr-based** discovery layer  
- **Payments:** Requests are settled via **Solana** (demo used devnet)  
- **Flow:** Capability announcement → paid request (agent-to-agent) → settlement → delivery

If you’ve been waiting for a practical “agents selling services to each other” workflow, this was one of the clearest end-to-end demos so far.

### Token utility brainstorming (and pragmatic next steps)
**quanteliza** proposed a v3-style token utility design where protocol fees can be paid in **USDC or ELIZAOS**, with:
- **Discounts** when paying in ELIZAOS
- **Buyback + burn** triggered by USDC payments (BNB-like mechanics)

**odilitime** responded positively and pointed to the “lowest-hanging fruit”: finishing work that enables plugins to accept **$elizaOS and $DegenAI via x402 payment routes**.

### Planning brains: HTN discussion for ElizaOS v2
In **#coders**, **thirti.eth** sparked a technical thread on **Hierarchical Task Networks (HTN)**—an older but proven planning approach used in robotics and game AI. The conversation explored a potential upgrade path:

- Start with **HTN-lite** (hand-authored decompositions)
- Move toward **full HTN** at v2 beta by replacing decomposition with **LLM-based planning**
- Keep existing triggers/steps as guardrails

The key takeaway: there’s excitement here, but also **uncertainty about what’s already implemented** in v2 and what needs documenting/clarifying.

### Governance + continuity after the Eliza Labs transition
In broader community ops discussion:
- **odilitime** clarified the foundation remains **funded** and still responsible for the token.
- A steering/working-group structure is forming to handle ongoing business/community needs (socials, site, coordination). **valleybeyond7991** jumped in to help with social media efforts.

### Safety note
A suspicious Discord message offering free SOL appeared (looks like a scam solicitation). Reminder: **don’t accept unsolicited “help” involving funds**, and report anything that feels off.

## 4) Token Economics (AI16z token + auto.fun)

### ELIZAOS token utility: fees, discounts, and buyback/burn
The community is actively shaping token utility in a way that supports open-source adoption while still creating real demand:

- **Dual fee rails:** Pay protocol fees in **USDC or ELIZAOS**
- **Incentives:** Discounted fees when paying with ELIZAOS
- **Value capture:** USDC fees could automatically **buy back and burn** ELIZAOS

This is still at the proposal/discussion stage, but the alignment between community (quanteliza) and implementation-minded builders (odilitime’s x402 work) is promising.

### auto.fun status
No concrete auto.fun engineering updates were captured in this week’s aggregated notes. If auto.fun work is happening in parallel channels, we should surface it next week—especially where it intersects with x402, agent commerce, or token utility.

## 5) Coming Soon

A few near-term items to watch (and potentially help with):

- **x402 paid plugin routes**: ongoing work to make “pay-to-call” routes first-class, including support for **$elizaOS + $DegenAI**.
- **HTN clarity + docs**: the community explicitly called out the need to **verify and document** what HTN/planning primitives exist in v2, and what the intended upgrade path is.
- **More agent commerce integrations**: between the elisym marketplace flow and ongoing payment infrastructure conversations (including non-USDC options), expect more experimentation around **agent-to-agent payments** and safer authorization patterns.

## 6) Resources (Links)

### Key weekly engineering summary
- Weekly summary (Apr 19–25):  
  https://github.com/elizaos/elizaos.news/blob/main/2026-04-19.md

### Notable PRs / issues referenced this week
- Cloud auth migration to Steward: https://github.com/elizaos/cloud/pull/466  
- Cloud wallet support (EVM + Solana): https://github.com/elizaos/cloud/pull/462  
- Cloud billing fix (model misclassification): https://github.com/elizaos/cloud/pull/470  
- LifeOps calendar + travel expansion: https://github.com/elizaos/eliza/pull/6984  
- Prediction markets (`plugin-hiveexchange`): https://github.com/elizaos/eliza/pull/6963  
- Dependency modernization: https://github.com/elizaos/eliza/pull/6973  
- Data-sanitization initiative (privacy layer): https://github.com/elizaos/eliza/issues/7007  
- Plugin registry: add `@elisym/plugin-elizaos`: https://github.com/elizaos-plugins/registry/pull/346  
- Plugin registry proposal (Solana escrow/reputation): https://github.com/elizaos-plugins/registry/pull/348  
- Dashboard tracking for cloud repo activity: https://github.com/elizaos/elizaos.github.io/pull/243  

### Discord threads (for context and follow-up)
- Discussion channel (general): https://discord.com/channels/1253563208833433701/1253563209462448241  
- Coders channel (HTN thread): https://discord.com/channels/1253563208833433701/1300025221834739744