# ElizaOS Developer Update (2026-03-15 → 2026-03-21)

This update summarizes developer-relevant changes and incidents observed across ElizaOS community engineering discussions and linked repos during the past week.

---

## 1) Core Framework

### Plugin naming standardization (xfn-framework + registry)
A naming refactor landed to reduce long-running confusion between singular/plural “form(s)” plugins:

- `plugin-form` → `plugin-form-chain`
- `plugin-forms` → `plugin-form`

This was accompanied by corresponding registry updates (per core dev discussion on 2026-03-18). If you have hard-coded package names in agent manifests, deployment configs, or import paths, review and update them.

**Migration checklist (recommended):**
- Search your codebase for `plugin-forms` and `plugin-form` (old meaning) references.
- Update package installs and runtime plugin lists to match the new canonical names.
- Rebuild/redeploy any ElizaCloud images after updating dependencies.

---

## 2) New Features

### Babylon: agent-driven market simulation (integration + tokenomics hooks)
Babylon launched as a market simulation where players command AI agents to:
- perform research,
- share information,
- make trades and predictions.

The launch includes a community airdrop and is expected to drive **ElizaCloud token buybacks** (as described by the team in Discord on 2026-03-20). While the tokenomics components are not developer APIs per se, Babylon is positioned as a “real workload” driver for ElizaCloud usage.

**Links**
- Discord discussion thread (Babylon launch context):  
  https://discord.com/channels/1253563208833433701/1253563209462448241

### Ensoul persistence plugin: encrypted decentralized agent state
A new persistence plugin was announced: `@ensoul-network/plugin-elizaos`, providing encrypted, decentralized storage for “agent consciousness” across a validator network.

Key technical properties (as presented):
- agent-owned encryption keys
- erasure-coded sharding across nodes
- “Ensouled Handshake” for cryptographic identity proof
- “consciousness age” trust metric (duration-based)

**Links**
- Docs: https://ensoul.dev/docs/quickstart.html  
- Explorer: https://explorer.ensoul.dev  
- Repo: https://github.com/suitandclaw/ensoul

> Developer note: treat this as an additional persistence backend. If you already implement memory/state using an existing ElizaOS storage adapter, evaluate how Ensoul’s identity proof and shard model maps to your state consistency requirements.

### Moltraffle plugin (community): permissionless on-chain raffles on Base
A new plugin was announced for Base: a USDC raffle system using Chainlink VRF, with actions:
- `LIST_RAFFLES`
- `GET_RAFFLE`
- `JOIN_RAFFLE`
- `CREATE_RAFFLE`
- `DRAW_WINNER`

The author recommends submitting a PR to the official registry for discoverability.

**Links**
- Registry repo (submit PR): https://github.com/elizaos-plugins/registry  
- Discord context (announcement + guidance):  
  https://discord.com/channels/1253563208833433701/1253563209462448241

**Example: adding a third-party plugin to your agent (conceptual)**
```bash
# From your agent project
pnpm add <moltraffle-package-name>
# or
npm i <moltraffle-package-name>
```

```ts
// agent.ts (conceptual)
import { moltrafflePlugin } from "<moltraffle-package-name>";

export const agent = createAgent({
  plugins: [
    moltrafflePlugin({
      chainId: 8453, // Base
      rpcUrl: process.env.BASE_RPC_URL!,
    }),
  ],
});
```

---

## 3) Bug Fixes / Incident Analysis (Critical)

### ElizaCloud disk image upload: client reports success, server receives nothing (under investigation)
A deployment-path issue was reported where disk images “upload” from the client side but do not appear on the server side. The stack in use was confirmed as:
- **ElizaOS CLI 1.x + ElizaCloud**

Current known state:
- server-side verification showed **no image received**
- root cause not yet identified (could be multipart handling, presigned URL flow, auth/session expiry, or proxy size/timeouts)

**Links**
- Discord engineering thread (coders):  
  https://discord.com/channels/1253563208833433701/1300025221834739744

**Suggested debugging steps (for affected developers)**
```bash
# 1) Verify CLI version
elizaos --version

# 2) Capture verbose logs if supported
elizaos deploy --verbose 2>&1 | tee deploy.log

# 3) If uploads use HTTP, confirm request size + server response codes with a proxy (mitmproxy) or curl reproduction
```

### ElizaCloud deployment failure: `Cannot find module '@elizaos/plugin-discord'`
A critical deployment failure was reported after configuring Discord via the GUI, resulting in the container failing with:
- `Cannot find module '@elizaos/plugin-discord'`

Hypothesis raised in debugging:
- the plugin package/folder may be missing from the container build context (e.g., not present in `/packages`, not installed, or excluded by build steps).

Operational pain point:
- user reported the container became “stuck” with no apparent GUI reload mechanism.

**Links**
- Discord context (2026-03-19):  
  https://discord.com/channels/1253563208833433701/1253563209462448241

**Workaround (until root cause is fixed): ensure explicit dependency install**
```bash
# In your agent repo before building the ElizaCloud image:
pnpm add @elizaos/plugin-discord
# or npm i @elizaos/plugin-discord
```

If your deployment system relies on a monorepo “packages/*” workspace, confirm the workspace actually includes `@elizaos/plugin-discord` at build time (and isn’t omitted by pruning/pack steps).

### Milady releases: GPG key + SHA256 checksum issues (release integrity)
Issues were reported around release signing/checksums (GPG key and SHA256 sums) in the Milady app repo. If you consume Milady artifacts in CI/CD, treat these releases as **non-verifiable** until corrected.

**Link**
- Milady repo: https://github.com/milady-ai/milady

---

## 4) API Changes (Developer-facing)

### Package name changes (plugin-form / plugin-forms)
If you import plugins or reference them by name in configuration, treat the refactor as an API surface change:

- Old → New:
  - `plugin-form` → `plugin-form-chain`
  - `plugin-forms` → `plugin-form`

**Example: updating imports**
```ts
// before (example)
import { formPlugin } from "@elizaos/plugin-forms";

// after (example)
import { formPlugin } from "@elizaos/plugin-form";
```

```ts
// before (example)
import { formChainPlugin } from "@elizaos/plugin-form";

// after (example)
import { formChainPlugin } from "@elizaos/plugin-form-chain";
```

> Validate the actual exported symbol names for each package in the updated registry entry and package README(s); the above shows the *expected* migration pattern based on the naming change discussed.

---

## 5) Social Media Integrations

### Discord plugin operational reliability (priority)
The Discord integration surfaced as a top operational issue this week due to the missing-module deployment failure on ElizaCloud. If you’re deploying agents that must be reachable on Discord, ensure:
- `@elizaos/plugin-discord` is explicitly included in your dependency graph
- the container build does not prune the package
- you have a rollback path when GUI configuration changes break the runtime

No notable Twitter / Telegram / Farcaster plugin changes were reported in the available activity this week.

---

## 6) Model Provider Updates

No provider integration changes (OpenAI/Anthropic/DeepSeek/etc.) were reported in the available GitHub/Discord activity for this week.

---

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

### Ongoing V1.x toolchain usage in production paths
Multiple reports confirm active use of **ElizaOS CLI 1.x** with ElizaCloud. If you are migrating to a V2 runtime or a new plugin registry layout, avoid mixing:
- V1-era plugin naming / packaging assumptions
- V2 registry identifiers and dependency resolution

### Breaking change: plugin identifiers
The plugin naming standardization is a practical breaking change for:
- agent manifests that list plugins by string identifier
- code that imports packages by the old names
- CI pipelines that prebuild images with cached lockfiles

**Action required:** update names, regenerate lockfiles, rebuild images, redeploy.

---

## References & Links (from this week’s activity)
- Babylon launch context (Discord): https://discord.com/channels/1253563208833433701/1253563209462448241  
- ElizaCloud disk image upload issue (Discord coders): https://discord.com/channels/1253563208833433701/1300025221834739744  
- Milady app repo (releases + checksum/signing issue context): https://github.com/milady-ai/milady  
- Ensoul plugin docs: https://ensoul.dev/docs/quickstart.html  
- Ensoul repo: https://github.com/suitandclaw/ensoul  
- Plugin registry (submit PRs like moltraffle): https://github.com/elizaos-plugins/registry