# ElizaOS Developer Update (2026-03-08 → 2026-03-14)

## 1) Core Framework

### Agent runtime initialization: plugin side-effects vs. explicit infrastructure wiring
This week’s main architectural thread was a runtime refactor proposal (shared via HackMD in Discord) focused on removing **infrastructure registration as plugin init side-effects**, and replacing it with **explicit dependency injection** during runtime construction.

**Problem observed (current behavior):**
- `plugin-sql` registers its DB adapter as a side-effect of `init()`.
- Plugin `init()` runs **in parallel**, so dependent plugins (e.g., `plugin-personality`) can execute before the adapter exists.
- Downstream apps (e.g., *milaidy*) implemented a defensive workaround: **pre-register `plugin-sql` before `initialize()`** to avoid the race.

**Proposed direction (refactor intent):**
- Make critical infrastructure (e.g., DB adapter) a **required constructor/runtime argument** rather than an implicit global/side-effect.
- Split “runtime setup logic” out of the runtime module so bootstrapping becomes deterministic and testable.
- Keep API complexity low during the refactor (explicitly called out as a constraint).

**Why this matters to developers:**
If you have plugins that assume other plugins “magically” registered shared components during initialization, expect those assumptions to be challenged as V2 runtime wiring becomes more explicit and deterministic.

---

## 2) New Features

### A) Scheduled agent wake-ups and Discord automation (cron-based)
Developers discussed production patterns for running Discord posting agents without manual triggers, using **cron triggers for agent wake-up**.

**Recommended approach by major version:**
- **ElizaOS v2.x:** use `plugin-cron`
- **ElizaOS v1.x (e.g., 1.7.2):** use `plugin-heartbeat`

This reflects a move toward a clearer scheduling primitive in v2.x (cron semantics) while v1.x commonly relies on periodic heartbeat loops.

#### Example: cron-driven “post to Discord” task (conceptual)
The shared implementation reference was a Spartan repo task file (e.g., `tsk_discord_post.ts`) used to run a periodic post.

```ts
// Conceptual example — align with your app’s task/action wiring.
// Intended to show the pattern: cron event -> agent wake -> run a post action.

export const discordScheduledPost = {
  name: "discordScheduledPost",
  schedule: "0 */3 * * *", // every 3 hours
  run: async ({ agent, discord }) => {
    const msg = await agent.generate({
      prompt: "Post a concise update to the dev channel.",
    });

    await discord.postMessage({
      channelId: process.env.DISCORD_CHANNEL_ID!,
      content: msg,
    });
  },
};
```

Operational guidance from Discord discussion:
- Cron schedules in the **1–3 hour** range were reported as stable for autonomous operation patterns (OpenClaw-style agents).
- If you’re on **1.7.2**, expect some adaptation work when borrowing v2.x examples.

---

### B) PumpFun buybacks plugin (Solana payments + automated buybacks)
A new plugin was announced enabling **tokenized agent buyback payments** on Solana via **PumpFun’s automated buyback system**. This is positioned as an agent monetization/payment-rail integration that ties agent revenues to buyback mechanics.

> Status note: announcement-only in Discord this week; no PR link was provided in the aggregated data.

---

### C) Agent discovery: public registry + “skill.md” integration
An “open agent registry” with autonomous orchestration was discussed and demoed at:
- https://aiprox.dev

Key technical traits described:
- REST-based self-registration and discovery
- Multi-rail payments (Lightning / Solana / x402)
- Usage-based rating + auto-approver scoring (1–10) for new registrations
- Reported: 14 live agents

**Endpoints referenced:**
- `POST /api/agents/register`
- `GET /api/agents`

**Discovery integration with agentskills.io:**
A lightweight discovery hook was implemented by adding a `skill.md` file at the domain root (e.g., `https://aiprox.dev/skill.md`) for crawlers like openclaw/Hermes-agent.

---

### D) Git branch “story” analysis tool (developer tooling)
A tool to analyze git branches and generate “branch stories” was demonstrated:
- PR: https://github.com/elizaOS/prr/pull/5

This is useful for:
- summarizing deltas across long-running branches (0.x → 1.x → 2.x),
- generating human-readable progress narratives for releases and migrations.

---

## 3) Bug Fixes (and critical mitigations)

### Plugin initialization race condition (sql adapter availability)
While not confirmed as “fixed” in core this week, the issue was clearly identified and mitigated in downstream usage:

- **Root cause:** parallel plugin initialization + side-effect registration of core infrastructure (DB adapter).
- **Symptom:** dependent plugins can run before DB adapter exists.
- **Mitigation:** manual pre-registration/ordering in the application bootstrap.
- **Planned fix:** refactor runtime so required infra is passed explicitly (constructor args), eliminating the race class entirely.

**Developer takeaway:**
If you have any plugin that:
- reads from a shared singleton registry set during another plugin’s `init()`, or
- assumes init ordering,
you should treat that as a latent race and plan to migrate toward explicit dependency wiring.

---

### Security/operational: migration scam attempts (community mitigation)
Repeated scam attempts were reported around token migration support (fake support bots and seed-phrase prompts). While not a code bug, it affects developer ops/support automation:
- Migration window is **closed** (per Discord guidance; closed Feb 4, 2026 after a 3-month period).
- Users seeking “late migration” are being targeted.
- Guidance: never request seed phrases; ensure your official bots/docs don’t link to unverified domains.

---

## 4) API Changes

### No merged API diffs provided in this week’s aggregated GitHub activity
However, the **runtime refactor proposal** implies upcoming API surface changes around:
- runtime construction and bootstrap (more explicit setup),
- plugin initialization expectations,
- DB adapter provisioning (moving from implicit registration → explicit required argument).

**Action for plugin authors:**
Start auditing your plugins for:
- reliance on side-effect registration,
- implicit global registries,
- init-time ordering assumptions.

---

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

### Discord
- Most concrete integration work this week centered on **Discord scheduling/automation** using cron/heartbeat patterns (see §2A).
- DM utility patterns were referenced (Spartan examples), aimed at improving agent-to-user interactions via private messages.

### Twitter / Telegram / Farcaster
- No plugin-level code changes were captured in the provided weekly data.
- A future-facing content pipeline was discussed (video briefings; potential Grok/X news integration), but no PRs/issues were linked this week.

---

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

No model provider integration changes, upgrades, or breaking provider API notes were surfaced in the provided GitHub/Discord activity for this week.

---

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

### Scheduling primitives differ by major version
- **V1.x:** common pattern uses `plugin-heartbeat` (interval-based loops).
- **V2.x:** recommended pattern uses `plugin-cron` (cron semantics; wake-up triggers).

If you port agents from 1.7.2 → 2.x:
- expect refactors from “every N minutes” heartbeat logic to cron schedules,
- validate task registration and runtime hooks, since V2 is converging on more explicit runtime wiring.

### Upcoming runtime refactor may break “side-effect init” plugins
If the proposed runtime changes land, plugins that:
- register infra during `init()` as a side-effect, or
- assume “DB adapter will exist by the time I run”
may break or require migration to explicit dependency injection.

---

## References / Links
- Git branch analysis tooling PR: https://github.com/elizaOS/prr/pull/5  
- Docs PR mentioned for cloud content (referenced in Discord): https://github.com/elizaos/elizaos.github.io/pull/243  
- Public agent registry discussed: https://aiprox.dev  
- Babylon ticker mentioned: https://play.babylon.market/ticker