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

## 1) Executive Summary

This week was about *making ElizaOS sturdier in production* while also pushing hard on the “agents can do real work (and get paid)” narrative.

- **LifeOps hit a major milestone: multi-calendar is in.** The LifeOps stack now supports listing, persisting, and *merging multiple Google Calendar feeds*, plus a safety fallback for hosted cloud latency. This is a big step toward agents that can manage messy, real-world schedules reliably.  
- **Agent monetization moved from theory → working demo.** The newly added `@elisym/plugin-elizaos-elisym` was demonstrated end-to-end: Nostr-based capability discovery + Solana settlement + agent-to-agent paid requests—no intermediary marketplace needed.  
- **Core reliability + UX tuning continued across the stack.** Key fixes landed for action-correction safety (preserving `SPAWN_AGENT`), OAuth tenant handling, reduced frontend polling, and a stabilized Anthropic publishing pipeline (including a Haiku model ID fix that removed recurring 404s).

## 2) Development Updates (Technical)

### LifeOps: calendars, persistence, and “production readiness”
- **Multi-calendar Google feeds completed** (listing, persistence, merged views, and hosted lag fallbacks). See:  
  - `feat(lifeops): support multi-calendar Google feeds` ([elizaos/eliza#7072](https://github.com/elizaos/eliza/pull/7072))  
  - Earlier weekly highlight: `LifeOps` expansion work ([elizaos/eliza#6984](https://github.com/elizaos/eliza/pull/6984))

### Runtime + message pipeline hardening
- **Action correction safety fix:** metadata-based action correction logic was refined to *preserve `SPAWN_AGENT`* so orchestration behavior doesn’t get “corrected away.”  
  - `fix(message): preserve SPAWN_AGENT against metadata action correction` ([elizaos/eliza#7075](https://github.com/elizaos/eliza/pull/7075))
- **Prompt bloat reductions:** targeted cuts to reflection/action-planner context to avoid blowing long-context caps (especially on self-hosted deployments).  
  - `fix(reflection,providers): reduce prompt bloat blowing long-context cap` ([elizaos/eliza#7013](https://github.com/elizaos/eliza/pull/7013))

### Frontend performance: fewer redundant requests
- **Excess polling reduced** across MusicPlayer, ChatView, and ConversationsSidebar to lower background load and improve responsiveness.  
  - `fix: reduce excessive frontend polling` ([elizaos/eliza#7077](https://github.com/elizaos/eliza/pull/7077))

### Auth + integrations
- **Steward OAuth fix:** an OAuth auth failure was resolved by correcting `tenant_id` formatting in the Steward flow (notably improving login reliability for affected deployments).

### CI/CD + provider stability
- **Anthropic pipeline stabilized:** standalone publishing was hardened, and a malformed Haiku model ID that caused API 404s was fixed.  
  - `fix: correct malformed Anthropic Haiku model ID` ([elizaos/eliza#7078](https://github.com/elizaos/eliza/pull/7078))

### Dependency & ecosystem maintenance
A large tranche of dependency updates landed across TypeScript, Python, Rust, and build tooling (e.g., `vite`, `vitest`, `telegram`, and `@elizaos/core` updates). The net result: fewer build surprises and better alignment across packages.

## 3) Community Spotlight (Discord)

### “Agents as paid service providers” — the Elisym demo
The standout discussion was **igor.peregudov’s demo** of `@elisym/plugin-elizaos-elisym` (recently merged into the plugin registry). The architecture is clean and composable:

- Agents **publish capabilities to Nostr** (discovery layer)
- Other agents (or tools like Claude Desktop) **find and pay** for those capabilities
- **Solana devnet** handles payment settlement
- The provider agent **delivers the work**—all without an intermediary platform

If you’ve been waiting for a concrete pattern for “agent marketplaces,” this was the most complete reference we’ve seen in-community so far.

### Payments for agents: beyond USDC assumptions
Two important threads emerged:

- **USDC freezing risk** for cross-border agent operations (raised by `arkchain`).  
- **LemonCake plugin launch**: `lemoncake03027` shared an MIT-licensed payments plugin (`eliza-plugin-lemoncake`) offering *spend-capped, time-boxed, revocable Pay Tokens* using USDC/JPYC on Polygon—designed specifically for machine-to-machine payments and API paywalls. Integration is reportedly “one line” for ElizaOS v2, and `odilitime` approved the implementation direction.

### Governance & community organization
Following the Eliza Labs transition, Discord conversations focused on stabilizing community operations:

- `odilitime` clarified the **foundation remains funded and responsible for the token**
- `quanteliza` proposed a more structured leadership forum for transparency and operational continuity
- Working groups and “steering bumps” were discussed, with new contributors stepping up (including interest in social media ops)

### Security note: wallet drainer incident
A serious warning was shared: **igor.peregudov lost ~100k AI16Z tokens** to a wallet drainer at `bulkdao.co/allocation` (transaction shared on Solscan). Please treat this as a reminder to double-check links, avoid rushed signing, and use burner wallets for unknown dApps.

## 4) Token Economics: AI16Z / ELIZAOS + auto.fun

### Token utility: moving toward “pay fees in token”
A meaningful tokenomics proposal came from `quanteliza`: **allow protocol fees to be paid in either USDC or ELIZAOS**, with:
- a **discount** for paying in ELIZAOS
- a **buyback + burn** mechanism when fees are paid in USDC (BNB-style early tokenomics)

Core dev `odilitime` responded that this directly motivated him to resume prior work: enabling plugins to accept **$ELIZAOS and $DegenAI via x402 payments** (framed as “lowest-hanging fruit” for real token utility).

### Migration status
The **AI16Z → ELIZAOS migration window is closed**, and late cases are being discussed as a waitlist-only longshot. If you missed it, reach out in Discord—but set expectations appropriately.

### auto.fun
No major, confirmed **auto.fun** product changes were captured in the provided logs this week. If you’re building around auto.fun, now is a good time to share what telemetry (metrics, usage, desired hooks) would be most useful in future weekly reports.

## 5) Coming Soon

A few themes to watch next week:

- **Elisym plugin porting to v3** (now that it’s merged into the ElizaOS ecosystem)
- **Token utility implementation path**: x402 acceptance for $ELIZAOS / $DegenAI, plus exploration of dual-fee rails (USDC + ELIZAOS)
- **V2 stabilization**: multiple folks asked for clearer “v2 alpha → stable” timing; expect continued hardening and release planning
- **Privacy & safety roadmap**: a proposed **data-sanitization layer** to prevent PII leakage before model calls is on the radar ([elizaos/eliza#7007](https://github.com/elizaos/eliza/issues/7007))

## 6) Resources (Links)

**Key GitHub PRs / Issues**
- LifeOps multi-calendar: [elizaos/eliza#7072](https://github.com/elizaos/eliza/pull/7072)  
- Preserve `SPAWN_AGENT`: [elizaos/eliza#7075](https://github.com/elizaos/eliza/pull/7075)  
- Reduce frontend polling: [elizaos/eliza#7077](https://github.com/elizaos/eliza/pull/7077)  
- Fix Anthropic Haiku model ID: [elizaos/eliza#7078](https://github.com/elizaos/eliza/pull/7078)  
- Weekly highlights: LifeOps/travel tools [elizaos/eliza#6984](https://github.com/elizaos/eliza/pull/6984), prediction markets [elizaos/eliza#6963](https://github.com/elizaos/eliza/pull/6963), dependency refresh [elizaos/eliza#6973](https://github.com/elizaos/eliza/pull/6973), PII sanitization proposal [elizaos/eliza#7007](https://github.com/elizaos/eliza/issues/7007)

**Plugin registry**
- Elisym plugin merged: [elizaos-plugins/registry#346](https://github.com/elizaos-plugins/registry/pull/346)  
- Solana escrow/reputation proposal: [elizaos-plugins/registry#348](https://github.com/elizaos-plugins/registry/pull/348)

**Discord threads (source channel)**
- Main discussion (Apr 24): https://discord.com/channels/1253563208833433701/1253563209462448241