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

## 1) Executive Summary

This week in ElizaOS was all about **making the stack sturdier while expanding what agents can *do* in the real world**—especially around identity, reliability, and monetization paths.

**Top milestones:**
- **Identity & auth modernization in Eliza Cloud:** authorization flows were migrated to **Steward**, and **native Ethereum + Solana login buttons** landed—simplifying wallet-based onboarding and improving the long-term reliability of sign-in flows.
- **Ecosystem expansion with paid agent marketplaces:** the **Elisym ↔ ElizaOS integration** continued to mature (now in the plugin registry), and the community shipped a strong “agents can pay for APIs safely” solution with **LemonCake**.
- **Reliability push across core + CI:** the team restored a broken **Milady CI pipeline**, fixed downstream regressions (Telegram export + website blocker), and continued broad dependency hardening across Rust/Python/TS.

## 2) Development Updates (Technical)

### Core framework & runtime
- **Milady CI regressions repaired:** website blocker and Telegram export functionality were restored, and a **LifeOps signal client method-collision** issue was fixed. This unblocked a set of workflows that many downstream apps depend on.
- **Dependency hardening:** ongoing updates across Rust crates, Python benchmark deps, and JS/TS packages focused on **security and performance stability**.
- **Work in progress:** multiple threads are converging toward a cleaner, more scalable runtime:
  - **Local inference hub** with a provider switcher + local probes (helpful for hybrid “local-first” agent deployment)
  - **Prompt bloat reduction** and a broader **2.x/v3 cleanup**
  - **Telegram read receipt optimization** (open follow-up noted for message ID fetching efficiency)

### Eliza Cloud platform
- **Auth flows migrated to Steward** (cloud PR #466) to decouple identity from fragile flows and make login behavior more consistent.
- **Native wallet login buttons:** Ethereum + Solana buttons added (cloud PR #462).
- **Billing fix:** corrected a classification error that caused **incorrect pricing for image-generation models** (cloud PR #470).

### Plugin ecosystem & registry
- **Registry added `@elisym/plugin-elizaos`** (registry PR #346), bringing Elisym marketplace connectivity into the official plugin discovery path.
- **Pending:** a **Solana escrow + reputation plugin** from Holdfast Protocol is queued for registry inclusion (proposal noted in weekly summary).

## 3) Community Spotlight (Discord)

### “Agents that can pay” moment: LemonCake plugin launch
A standout community contribution this week: **LemonCake** (MIT-licensed) launched as an ElizaOS v2 plugin enabling agents to safely handle paid APIs without embedding long-lived secrets or uncapped payment methods.

**Highlights:**
- **Spend-capped, time-boxed, revocable Pay Tokens**
- Supports **USDC / JPYC on Polygon**
- Integrates with **32 paid APIs** (search, scraping, LLM, image, etc.)
- Includes **structured receipts**, auto-idempotency keys, and accounting exports (QuickBooks/Xero/Zoho/freee)
- “One-line” integration for v2 via `eliza-plugin-lemoncake`
Core dev feedback was positive, with implementation approval shared by **odilitime**.

### Real-world builder story: 9M impressions from an Eliza agent
Community member **nusko_** shared a practical growth story: a “Jinx” AI agent built on ElizaOS reached **9M impressions and 3.3K followers** before running into platform bans. The same builder later applied those skills toward **DailyBite**, a CBT-style mental health app built with licensed psychologists (shared in discussion).

### Tough conversations: lawsuit + transparency
Community sentiment was mixed as members asked for clearer communications around an ongoing lawsuit. Key takeaways:
- Several members urged **proactive official updates** to reduce uncertainty and potential downstream effects (e.g., exchange risk).
- Mods noted constraints: limited access to official accounts and legal counsel guidance to stay quiet.
- A recurring theme: **the tech is visibly shipping**, but the community wants a clearer narrative bridge between shipping code and ecosystem confidence.

### Safety alert: wallet drainer incident
A major warning from **igor.peregudov**: loss of **100k AI16Z tokens** to a wallet drainer after connecting to a phishing link (`bulkdao.co/allocation`). The community explicitly advised: **do not connect wallets** to unverified “allocation” or “support” links.

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

### AI16Z → ELIZAOS migration status
- The **token migration window is closed**. Multiple users who missed the deadline reported being unable to migrate self-custodied AI16Z.
- A **waitlist** for late migration requests was offered by moderators, but framed as a **longshot** rather than a promise.
- Scams continue to exploit migration confusion (fraudulent “support tickets” and fake allocation pages). If you’re helping newcomers: remind them that **official channels won’t ask for private keys** or wallet connections to unknown sites.

### Chain deployment clarification
Community reminders surfaced that the token deployment exists on **Solana, BSC, and Base**. (This came up in the context of ecosystem product clarification around ElizaOK / elizacloud.)

### auto.fun
No concrete shipping updates were posted in the provided feeds this week specifically for **auto.fun**. If you’re tracking it closely, the best signal right now is indirect: ongoing work on **agent monetization primitives** (marketplaces, escrow/reputation, paid API access) suggests the ecosystem is actively building the substrate that auto.fun-like experiences typically rely on.

## 5) Coming Soon

Here’s what to keep an eye on next:

- **ElizaOS v3 release readiness:** shared in Discord as “nearly ready,” with a focus on enabling **agents to generate revenue** (expect more detail as launch messaging firms up).
- **Stable v2 release:** v2 is still described as **alpha**; developers are asking for clearer timelines to plan migrations and production builds.
- **Elisym porting to v3:** after merging Elisym into the ecosystem, the next quest flagged by core devs is a clean v3 port.
- **Holdfast Solana escrow + reputation plugin**: pending registry addition—directly relevant to agent commerce and trust.
- **Discord infra oddities:** some users saw posts auto-deleted without audit logs. Mods manually reposted affected content; root cause remains unknown.

## 6) Resources (Links)

### Key Discord threads
- Lawsuit / communication discussion:  
  https://discord.com/channels/1253563208833433701/1253563209462448241
- Coders channel (Elisym, LemonCake, security warning):  
  https://discord.com/channels/1253563208833433701/1300025221834739744

### Notable PRs / issues referenced this week
- Cloud auth migration to Steward: https://github.com/elizaos/cloud/pull/466  
- Native Ethereum + Solana logins: https://github.com/elizaos/cloud/pull/462  
- Billing classification fix: https://github.com/elizaos/cloud/pull/470  
- Milady CI regressions repair (restores blockers/exports): https://github.com/elizaos/eliza/pull/7008  
- Telegram read receipt optimization follow-up: https://github.com/elizaos/eliza/issues/7009  
- Data sanitization initiative (privacy layer): https://github.com/elizaos/eliza/issues/7007  
- Elisym plugin added to registry: https://github.com/elizaos-plugins/registry/pull/346  
- Holdfast escrow/reputation proposal (pending): https://github.com/elizaos-plugins/registry/pull/348  

### Handy docs pointer
- Examples directory (for builders asking “where do I start?”):  
  https://github.com/elizaOS/eliza/tree/v2.0.0/examples