# Fact Briefing: 2026-05-13

## Overall Summary
Technical efforts are currently focused on resolving a major outage of the v2 plugin registry while addressing security concerns regarding compromised Discord accounts. Strategic infrastructure hardening continues with the migration of the Slack plugin into the monorepo and the implementation of @elizaos/vault for cross-platform secrets management.

## Key Facts

- The v2 plugin registry infrastructure (elizaos-plugins/registry and plugins.elizacloud.ai) is currently inaccessible, returning 404 errors.
- Core developer odilitime is considering a policy reversal to accept plugin PRs directly to the elizaOS/eliza repository due to registry infrastructure failure.
- PR #7197 introduced @elizaos/vault, a new package for AES-256-GCM encrypted secrets management using OS keychains.
- The Slack plugin was migrated into the monorepo in PR #7375, adding 11 actions and 120 unit tests.
- Operational costs for running Eliza Twitter bots have decreased from roughly $100 to $10 per month depending on reply volume.
- A developer requested sandbox testing for a Python-based multi-agent orchestrator utilizing the Model Context Protocol (MCP).
- Security vulnerabilities were identified in the Discord server involving compromised admin accounts and scammer activity.
- Missing database table definitions in plugin-sql for entity_identities and fact_candidates were identified as the cause of 'internal parsing error' failures.

## Open Questions

- Is the v2 registry infra still private pending the 2.0.0-beta launch?
- Should I hold my PR until the repo goes public?
- Did Shaw remove ElizaOS from his X bio?
- Has something been compromised in the coders channel?

## Categories

### Twitter News Highlights
- Community noted that Shaw removed ElizaOS from his X bio, though no official response followed. (Sentiment: neutral)

### GitHub Updates

#### New Issues/PRs
- [Pull_request #7197: feat(vault): @elizaos/vault — cross-platform secrets vault + Settings UI integration](https://github.com/elizaos/eliza/pull/7197) by Dexploarer - Status: merged - Significance: Implements secure, encrypted-at-rest secrets management to replace plaintext storage in config files.
- [Pull_request #7375: feat(slack): migrate plugin-slack into the monorepo](https://github.com/elizaos/eliza/pull/7375) by 2-A-M - Status: merged - Significance: Consolidates Slack connectivity into the monorepo, resolving the last major-platform standalone connector issue.
- [Pull_request #7376: feat(cloud): support monetized container app domains](https://github.com/elizaos/eliza/pull/7376) by NubsCarson - Status: merged - Significance: Adds production path for agent-built monetized apps and Cloudflare-managed domain support.
- [Issue #7222: plugin-sql runtime-migrator missing drizzle pgTable defs for entity_identities](https://github.com/elizaos/eliza/issues/7222) by Sw4pIO - Status: closed - Significance: Identified a critical bug causing chat failures on fresh database installs due to missing schema definitions.

#### Overall Focus
- Focus on hardening core infrastructure, improving system reliability for headless environments, and consolidating the plugin ecosystem into the monorepo.

### Discord Updates
- **#coders:** Technical debate regarding the failure of the v2 registry infrastructure. Developers are unable to submit new plugins due to 404 errors on the registry repository. (Key Participants: thegreatluna8713, odilitime)
- **#discussion:** Introductory greetings and requests for sandbox testing of Python-based orchestrators. General community sentiment is focused on onboarding new talent. (Key Participants: rma_bot, odilitime)

### User Feedback
- Users reported difficulties with the plugin submission process specifically for BUSL-1.1 licensed code which cannot be submitted directly to the monorepo. (Sentiment: negative)
- Strong interest in testing multi-agent orchestrators with Model Context Protocol (MCP) integrations. (Sentiment: positive)

### Strategic Insights

#### Plugin Registry Bottleneck
The failure of the centralized v2 registry infrastructure is causing a backlog of third-party plugin submissions and forcing a retreat to monorepo PRs.

*Implications/Questions:*
  - Does the current registry model create a single point of failure that compromises decentralization?

#### Operational Cost Efficiency
The 90% reduction in Twitter bot operational costs makes the platform significantly more accessible for long-tail developers and small projects.

*Implications/Questions:*
  - Will lower costs lead to an influx of low-quality or spam-oriented bot deployments?

### Market Analysis
- Community members noted Shaw (a key figure) removed ElizaOS from his social media bio amid favorable market conditions looking for a catalyst. (Relevance: Could signal a shift in leadership focus or lead to community FUD regarding project backing.)