# Fact Briefing: 2026-05-14

## Overall Summary
Development has shifted focus toward Elizabeth v3 infrastructure stabilization and the launch of the Qwen3.5-based Eliza-1 model series. Key technical challenges emerged regarding the v2 plugin registry infrastructure, resulting in persistent 404 errors and a potential revert to monorepo PRs.

## Key Facts

- The Eliza-1 model series based on Qwen3.5 was released, offering parameter sizes from 0.6B for mobile to 27B with a 1 million token context window.
- A new 0.8B Eliza-1 model is currently being trained using H200 hardware.
- The v2 plugin registry encountered 404 errors on elizaos-plugins/registry and plugins.elizacloud.ai, halting third-party submissions.
- GODL protocol proposed an integration with elizaos using a skill.md format, which was confirmed as directly compatible by maintainers.
- Security issues involving compromised admin accounts and scammer activity were identified within the Discord server.
- Python-based multi-agent orchestrator testing was approved for a sandbox channel using the A2A-protocol.
- Monthly hardening efforts in May successfully transitioned plugins to a modern ESM-first modular build structure.
- The Jupiter integration was migrated to an official API endpoint with mandatory security key authentication.

## Open Questions

- Is Eliza v3 development currently prioritizing infrastructure stabilization or the public release of the autonomous agent workflow stack?
- What is the integration status of the new identity/AgentID system in the Eliza v3 architecture?
- Can plugins with BUSL-1.1 licensing be submitted if the registry infrastructure remains inaccessible?

## Categories

### GitHub Updates

#### New Issues/PRs
- [Pull_request #7197: @elizaos/vault — cross-platform secrets vault + Settings UI integration](https://github.com/elizaos/eliza/pull/7197) by Dexploarer - Status: merged - Significance: Introduced encryption-at-rest for sensitive configuration, moving away from plaintext storage in config.env.
- [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: Critical bug that made chat unusable on fresh PGLite databases due to missing table schemas.

#### Overall Focus
- The project focus for May centered on foundational hardening, specifically stabilizing agent runtimes for headless environments and ensuring ESM-first architecture alignment.

### Discord Updates
- **#discussion:** Focus on the Eliza-1 model series specifications and inquiries regarding the v3 development roadmap and identity systems. (Key Participants: zadayos, mahmoudamer7645)
- **#coders:** Negotiations for GODL protocol integration, focusing on on-chain mining mechanics and autonomous staking strategies. (Key Participants: blankey1717, odilitime)

### User Feedback
- Developers reported high frustration with the new v2 plugin registry due to 404 errors preventing deployment of third-party tools. (Sentiment: negative)

### Strategic Insights

#### Model Hardware Diversification
By releasing models ranging from 0.6B to 27B, the project is positioning itself to capture both edge/mobile use cases and server-side high-context agent workflows.

*Implications/Questions:*
  - Does the infrastructure support seamless switching between edge and cloud models for a single agent identity?

### Market Analysis
- Introduction of the GODL protocol suggests an increasing intersection between autonomous agents and gamified on-chain mining on Solana. (Relevance: Provides a new utility and revenue generation vertical for elizaOS agents.)