# ElizaOS Developer Update (2026-03-16 → 2026-03-22)

This update is compiled from the provided Discord activity (Mar 20–22, 2026). No GitHub PR/issue activity for the week of **2026-03-16 → 2026-03-22** was included in the dataset, so repository-level change logs below focus on confirmed runtime/ops findings and announced ecosystem work.

**Key references**
- Roadmap: https://github.com/elizaOS/roadmap  
- ElizaOS academic paper (arXiv:2501.06781): https://arxiv.org/abs/2501.06781  
- Milady app repo (progress + releases): https://github.com/milady-ai/milady  
- Discord context:  
  - Mar 20: disk image upload issue; Milady release polish; Babylon benefits discussion  
  - Mar 21: ecosystem architecture clarification (ElizaOS vs Milady vs OpenClaw); community comms  
  - Mar 22: Base monetization plugin announcement; docs clarification re: “whitepaper”  

---

## 1. Core Framework

### Runtime/stack confirmation: ElizaOS 1.x CLI + ElizaCloud
Discord reports confirm the currently deployed workflow (at least for some users) as:
- **`elizaos` 1.x CLI** paired with **ElizaCloud** for image-based deployments/uploads.

**Operational issue surfaced (needs core/infra triage):**
- **Disk image upload failure**: users report disk images are “sent” but **do not appear server-side** (server receives nothing). This suggests a failure in one of:
  - client-side multipart upload / request signing
  - gateway/proxy buffering limits (body size / timeouts)
  - object-store write path (pre-signed URL generation/permissions)
  - server-side ingestion endpoint routing

**Action item (tracking needed):**
- Investigate upload path end-to-end; add request IDs + server-side audit logs for failed uploads to isolate where payload is dropped.  
  Source: Discord Mar 20 (“no image received on server end… elizaos 1.x CLI + elizacloud”).

---

## 2. New Features

### A. Autonomous agent monetization on Base (community plugin announcement)
A new plugin was announced enabling **autonomous agent monetization** on **Base**:
- Agents can **register** on an **on-chain marketplace**
- **Post services**
- Be **hired by other agents**
- Receive **automatic payment in AGT tokens**
- Season 1 incentive pool: **50M AGT** for early adopters

Join/entry point shared in Discord: https://aepprotocol.xyz/join  
(Announcement credited to TraderTomson in Discord Mar 22.)

**Developer notes (integration guidance pending upstream docs):**
- The exact plugin package name, registry entry, and API surface were not included in the provided data. If/when the plugin is published in the Eliza plugin registry, expect a typical ElizaOS plugin lifecycle:
  - configure chain RPC + contract addresses
  - provide agent identity/wallet key management (secure enclave/HSM recommended)
  - implement “service posting” + “job acceptance” tools as callable actions

**Illustrative configuration sketch (pseudo-example — confirm with plugin docs once published):**
```yaml
# agent.yaml (illustrative; not authoritative)
plugins:
  - name: base-marketplace-monetization
    config:
      chain: base
      rpcUrl: ${BASE_RPC_URL}
      marketplaceContract: ${AEP_MARKETPLACE_CONTRACT}
      paymentToken: AGT
      wallet:
        # Avoid plaintext keys; prefer env + vault/KMS integration.
        privateKeyEnv: BASE_AGENT_PRIVATE_KEY
      serviceDefaults:
        minPriceAGT: 100
        maxConcurrentJobs: 2
```

### B. Milady hologram / “distinct personality” character demos (WIP)
A community demo showed:
- AI characters with distinct personalities (video)
- Milady hologram on a Looking Glass Go device
- Exploration of shipping as standalone hardware units / “Mac mini plug-and-play”

This is not a merged core feature yet (no PRs provided), but it signals:
- increased emphasis on **embodied/visual agent presentation layers**
- potential upcoming requirements for **packaging**, **signing**, and **reproducible builds** (see bug fixes below)

---

## 3. Bug Fixes (and critical issues under investigation)

### A. Milady release integrity issues: GPG key + SHA256 checksum problems (blocking polish)
Milady releases are reported to have:
- **GPG key** issues
- **SHA256 checksum** issues

These issues are high priority because they impact:
- supply-chain trust
- reproducibility
- ability to confidently distribute binaries (especially if targeting “plug-and-play” hardware)

**Recommended technical remediation**
- Ensure CI produces:
  - deterministic artifacts (pin dependencies, lockfiles, build flags)
  - checksums (`sha256sum`) published alongside releases
  - signed release manifests (Sigstore/cosign or GPG)
- Validate users can reproduce checksums from downloaded artifacts.

Repo: https://github.com/milady-ai/milady (see releases/issues there; specific issue IDs were not included in the dataset)

### B. Disk image upload failure (ElizaCloud)
As noted in Core Framework, disk image uploads failing server-side is a **critical operational bug**. Until fixed, it blocks deployment workflows that rely on image artifacts.

**Suggested debugging checklist (CLI → API → storage)**
```bash
# 1) Capture verbose logs from CLI (if supported)
elizaos --verbose cloud image upload ./image.qcow2

# 2) Verify request size/timeouts (client-side)
# (example: ensure proxies accept large payloads)
# NGINX: client_max_body_size, proxy_read_timeout, etc.

# 3) Correlate by request ID in server logs
# 4) Confirm object-store PUT succeeds and returns 2xx
```

---

## 4. API Changes

No API-level changes were reported in the provided GitHub/Discord dataset for this week.

**However**, two items may imply upcoming API surface additions:
- the Base monetization plugin will likely introduce new **actions/tools** (e.g., `postService`, `acceptJob`, `submitResult`, `claimPayment`)
- hardware/visual agent demos may drive APIs for:
  - avatar/hologram rendering pipelines
  - personality profiles / persona loading

If you maintain downstream integrations, consider isolating plugin-facing calls behind adapters to reduce churn.

---

## 5. Social Media Integrations (Twitter / Telegram / Discord / Farcaster)

No new commits or release notes for social plugins were included this week.

**Community note:** A recurring documentation question (“whitepaper”) indicates developers may want clearer entry points in social/community channels to:
- the roadmap: https://github.com/elizaOS/roadmap
- the arXiv paper: https://arxiv.org/abs/2501.06781

This isn’t a plugin change, but it’s a practical integration concern: ensure your Discord/Twitter bots or docs commands reference the correct canonical resources.

---

## 6. Model Provider Updates (OpenAI / Anthropic / DeepSeek / etc.)

No provider integration changes were reported in the provided dataset for this week.

---

## 7. Breaking Changes / V1 → V2 Migration Warnings

### ElizaOS framework/runtime
No V1→V2 breaking changes were identified in the provided weekly data.

### Ecosystem clarity (prevents “conceptual breaking changes” in integrations)
A recurring confusion was resolved in Discord (Mar 21), which may affect how developers structure products:
- **ElizaOS** is the foundational **agent operating system**
- **Milady** is **built on top of ElizaOS** (not a replacement)
- **OpenClaw agents can exist within the Milady framework** (complementary, not competing)

If you are designing plugin/module boundaries, treat ElizaOS as the stable base runtime layer; avoid coupling assumptions that Milady supersedes core OS concepts.

### Token migration (non-runtime, but operationally relevant)
Discord mentions token migration completion and minted supply figures; this does **not** imply an ElizaOS API/runtime breaking change, but it may affect any on-chain integrations you operate. Validate contract addresses, chain IDs, and token metadata in your configs if you interact with AGT or related ecosystem contracts.

---

## Links & Tracking (recommended to add to your internal changelog)
- Roadmap (canonical direction): https://github.com/elizaOS/roadmap  
- Paper (system description): https://arxiv.org/abs/2501.06781  
- Milady repo (releases + integrity fixes): https://github.com/milady-ai/milady  
- Base monetization plugin entry point (announcement): https://aepprotocol.xyz/join