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

This update summarizes core engineering signals from GitHub activity and key developer discussions in Discord across the last week.

---

## 1) Core Framework (Architecture / Runtime / Plugin System)

### Framework vs SaaS boundary clarified (operational impact for builders)
Core maintainers reiterated that **ElizaOS is the open-source agent framework**, while **elizacloud** is the commercial SaaS that simplifies deployment and operations. This matters for contributors because some “platform” work (hosting, Spartan instances, customer data consolidation) may land outside the OSS repos and show up as operational changes rather than framework commits.

Developer context (Discord):
- elizacloud is intended to make agent rollout “push-button” while the core framework remains OSS.  
  Source: Discord discussion recap (2026-03-26)  
  https://discord.com/channels/1253563208833433701/1253563209462448241

### Planned environment consolidation (dev/prod → staging)
A platform infrastructure change was discussed: **collapsing production and development environments into a single staging environment** to manage “one Spartan instance” with customer data. If you deploy to elizacloud or rely on platform-hosted endpoints, expect:
- fewer environment-specific URLs
- stricter change control / release gating
- potentially different assumptions around “test data vs real data”

Status: discussed as an active initiative; no corresponding public PR referenced this week.  
Source: Discord discussion (2026-03-26)  
https://discord.com/channels/1253563208833433701/1253563209462448241

---

## 2) New Features (with implementation notes)

### New plugin: On-chain decision provenance via MultiversX (xProof)
A new plugin **xProof.app** was announced that **anchors agent decisions on-chain before execution**, producing an immutable timestamp *written by the chain* (not the agent). This is aimed at:
- auditability of autonomous agents (especially trading / market agents)
- non-repudiation and post-hoc verification
- “decision provenance” for high-stakes automations

**Registry PR:** `@elizaos/plugin-xproof`  
- PR: https://github.com/elizaos-plugins/registry/pull/266

**Install:**
```bash
npm install @elizaos/plugin-xproof @xproof/xproof
```

**Integration sketch (runtime/plugin registration)**
> Exact APIs may differ depending on your ElizaOS version and runtime bootstrap; treat as a conceptual reference until PR #266 is merged and docs are published.

```ts
import { AgentRuntime } from "@elizaos/core";
import { xProofPlugin } from "@elizaos/plugin-xproof";

const runtime = new AgentRuntime({
  plugins: [
    xProofPlugin({
      // plugin-specific config (e.g., cert issuance mode, app key)
      // The project notes: 10 free certificates available, no wallet required.
    }),
  ],
});

// Example: wrap a high-stakes action with provenance anchoring
runtime.on("decision:beforeExecute", async (decision) => {
  // xProof plugin anchors decision payload -> returns on-chain proof metadata
  const proof = await runtime.plugins.xproof.anchor({
    agentId: decision.agentId,
    intent: decision.intent,
    payloadHash: decision.payloadHash,
  });

  decision.metadata.provenance = proof; // e.g., tx hash / timestamp / cert id
});
```

Operational notes from the announcement:
- **10 free certificates** without requiring a wallet (useful for quick prototyping / hackathons).
- Provenance is anchored **before execution** (important for preventing “execute first, justify later” flows).

Source (Discord coders channel summary, 2026-03-26):  
https://discord.com/channels/1253563208833433701/1300025221834739744

---

### Pythia MCP server: verifiable on-chain indicators without API keys
A community release: **Pythia MCP server** enables agents to query **live market indicators directly from Chainlink oracles on Polygon**, avoiding API keys and off-chain market data pipelines. Indicators mentioned include EMA/RSI/VWAP/Bollinger Bands/volatility across multiple timeframes.

**Install:**
```bash
pip install pythia-oracle-mcp
```

**Why this matters for ElizaOS builders**
If you’re building:
- autonomous trading agents
- prediction-market agents (e.g., Babylon)
- risk monitors / liquidation sentries  
…this provides a more verifiable data path than typical REST market feeds.

Source (Discord, 2026-03-24):  
https://discord.com/channels/1253563208833433701/1253563209462448241

---

### Ecosystem: autonomous trading & agent “workspaces” patterns
Community builders shared designs that may influence recommended patterns:
- Autonomous trading agent experimentation and collaboration requests (Discord, 2026-03-25)
- An NFT-driven agent workspace system with deterministic personality mapping and a 3-tier MemGPT-style memory layout, claiming **ElizaOS V1 spec compatibility** (YAML frontmatter + `character.json` export)

These are not upstream framework changes this week, but they’re useful reference architectures for agent product teams.

Sources:
- https://discord.com/channels/1253563208833433701/1253563209462448241 (2026-03-25)
- https://discord.com/channels/1253563208833433701/1253563209462448241 (2026-03-24)

---

## 3) Bug Fixes (critical fixes with technical context)

### Security awareness: supply chain attack in `litellm-pypi`
A supply chain compromise affecting `litellm-pypi` was raised in community channels. No ElizaOS patch PR was referenced this week, but developers should treat this as an immediate action item:

**Recommended actions (if your agent stack touches LiteLLM or transitive deps):**
```bash
# Identify presence
pip show litellm || true
pip freeze | grep -i litellm || true

# If present, audit version + hashes and rotate secrets used on hosts
# Prefer pinned, hashed requirements in production.
```

Also consider:
- locking dependencies (hash checking)
- isolating runtime credentials (least privilege, short-lived tokens)
- scanning containers / SBOM generation

Source (Discord, 2026-03-24):  
https://discord.com/channels/1253563208833433701/1253563209462448241

---

## 4) API Changes (developer-facing)

No explicit core API signature changes were recorded in the provided GitHub/Discord activity for this week.

**Pending API surface (plugin registry):**
- If PR #266 is merged, expect a new registry entry and documented plugin interface for `@elizaos/plugin-xproof`. Track the PR for final exported types, config schema, and runtime hooks:
  - https://github.com/elizaos-plugins/registry/pull/266

---

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

No upstream changes to official social plugins (Twitter, Telegram, Discord, Farcaster) were referenced in GitHub activity this week.

Notes:
- Social channels were primarily used for ecosystem coordination, hosting announcements, and plugin disclosures rather than integration development.

---

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

No provider integration updates (new models, SDK changes, auth changes, rate-limit handling changes) were recorded in this week’s aggregated activity.

If you’re shipping production agents, continue to:
- pin provider SDK versions
- implement fallback routing (multi-provider) for critical tasks
- log provider request IDs for incident response

---

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

No new breaking changes were announced upstream this week.

### Migration caution (V1 compatibility claims in the ecosystem)
A community project explicitly referenced **ElizaOS V1 spec compatibility** (YAML frontmatter, `character.json` export). If you are migrating agents or “character” definitions:
- treat V1-format artifacts as **inputs that may require a normalization layer** in V2 runtimes
- add schema validation in CI to prevent silent runtime drift

**Action for maintainers/plugin authors:** consider publishing (or updating) a canonical “V1 character → V2 character” conversion guide once format deltas are finalized.

---

## Links (PRs / Discussions / References)

- Plugin registry PR (xProof): https://github.com/elizaos-plugins/registry/pull/266  
- Discord: general discussion (2026-03-24 to 2026-03-26 context):  
  https://discord.com/channels/1253563208833433701/1253563209462448241  
- Discord: coders channel (xProof + hosting announcement):  
  https://discord.com/channels/1253563208833433701/1300025221834739744  

---