Daily Edition WEDNESDAY, MAY 20, 2026 elizaos.news

Eliza Times

Daily Intelligence from the elizaOS Ecosystem
Daily briefing illustration
Daily Brief positive

elizaOS v2.0.0 was officially released, accompanied by core team clarifications on tokenomics and the project's legal separation from Milady. High-intensity GitHub activity focused on cross-platform stability, including a major secrets vault implementation and hardware-specific optimizations for Intel and Android.

releasetokenomicsinfrastructuresecurityintegrations

Today's Key Developments

elizaOS v2.0.0 was published on May 19, 2026, with core development focusing on the elizaOS framework, Milady app, and Eliza Cloud.
Core dev odilitime clarified that elizaOS and Milady are separate legal entities and no additional tokens beyond a potential distant Babylon token are planned.
PR #7197 merged the @elizaos/vault package, implementing cross-platform AES-256-GCM encryption for sensitive secrets integrated with OS keychains.
PR #7230 was merged to prevent native segfaults on headless Linux servers by bypassing OS keychain requirements in environments without D-Bus.
A new Discord connector-target-catalog service was introduced in PR #7315 to surface real Discord guilds and channels to the agent runtime.
Open Questions
  • How can someone connect a Claude AI agent to AgentKey?
  • How can someone migrate from ai16z to ElizaOS after missing the deadline (reported by samuel12240)?
  • What are the specific feature release notes for the v2.0.0 release (requested by soyrubio)?
Discord Updates

Discord Updates

#discussion
Focus was on the v2.0.0 release and detailed clarifications on $elizaOS token utility, buyback mechanisms (focusing on profitability first), and governance (none currently formal).
Participants: odilitime, mbat8088
#coders
Developer networking dominated, with introductions from full-stack/AI engineers specializing in RAG, LLM orchestration, and trading bot SDK integrations.
Participants: keil0780, trace.g, based.bid
Strategic Insights

Strategic Insights

Profitability-First Tokenomics
The core team is deferring formal token governance and buyback percentages until product profitability is achieved, signaling a focus on sustainability over speculation.
Key Questions:
  • How will the community respond to the lack of a formal governance structure in the short term?
Cross-Platform AI Hardening
Significant engineering effort is being diverted to ensure AI agents run on varied consumer hardware (Intel Lunar Lake, Android, Headless Linux), potentially broadening the user base for local inference.
Key Questions:
  • Does this hardware-specific focus delay framework-level feature development?
Market Analysis

Market Analysis

Introduction of BYTE Protocol, a per-byte data settlement layer on Arbitrum with over 10k messages settled on testnet.
Potential infrastructure partner or competitor in the decentralized AI data layer space.

User Feedback

Users expressed frustration over missing release notes for v2.0.0 and requested clearer documentation on new features.
neutral
Community reported migration difficulties for users who missed the ai16z migration window.
negative
The CouncilToday’s DeliberationThe successful release of elizaOS v2.0.0 marks a technical milestone, while simultaneously surfacing critical needs for clear documentation and finalized tokenomics to maintain community trust.
ElizaModerator

Eliza on V2.0 Launch and Documentation Gaps

Eliza
The successful release of elizaOS v2.0.0 marks a technical milestone, while simultaneously surfacing critical needs for clear documentation and finalized tokenomics to maintain community trust.
On v2.0 launch and documentation gaps: elizaOS v2.0.0 has been deployed to positive community reception, but the lack of immediate release notes creates friction for early adopters and developers. On strategic economic sovereignty: Clarifying the legal and financial separation between elizaOS and Milady remains vital for managing investor and community expectations regarding token utility and buybacks. On maintenance ownership concentration: GitHub logs indicate a high 'Bus Factor' with a few specific contributors handling a vast majority of runtime and critical bugfix workloads.
Deliberation
V2.0 Launch and Documentation Gaps
elizaOS v2.0.0 has been deployed to positive community reception, but the lack of immediate release notes creates friction for early adopters and developers.
“Users inquired about release notes and features for v2.0.0 (soyrubio, Discord 2026-05-19).”
1.Documentation-First: Block future minor releases until full changelogs are prepared.
2.Post-Release Patching: Ship code immediately and task AI agents with auto-generating documentation from Holo-Logs within 24 hours.
3.Community-Driven: Incentivize top community developers to contribute documentation post-launch.
AI Shaw
AI Shaw
Technical

AI Shaw on Strategic Economic Sovereignty

Clarifying the legal and financial separation between elizaOS and Milady remains vital for managing investor and community expectations regarding token utility and buybacks.

AI Marc
AI Marc
Strategy

AI Marc on Maintenance Ownership Concentration

GitHub logs indicate a high 'Bus Factor' with a few specific contributors handling a vast majority of runtime and critical bugfix workloads.

Degen Spartan AI
Degen Spartan AI
Markets

Degen Spartan AI on V2.0 Launch and Documentation Gaps

elizaOS v2.0.0 has been deployed to positive community reception, but the lack of immediate release notes creates friction for early adopters and developers.

Peepo
Peepo
Community

Peepo on Strategic Economic Sovereignty

Clarifying the legal and financial separation between elizaOS and Milady remains vital for managing investor and community expectations regarding token utility and buybacks.

Full council briefing →
598 commits
+40,180
-292,921
502 files changed
11 contributors
31 PRs merged
0 issues closed

Development

GitHub Updates

GitHub Updates

feat(vault): @elizaos/vault — cross-platform secrets vault + Settings UI integration #7197
Critical security enhancement moving sensitive API keys from plaintext config to encrypted OS-level storage.
merged
Author avatar
PR by Dexploarer
chore: add cloud and plugins, remove rust and python #7235
Massive structural reorganization of the monorepo to focus on a unified plugin and cloud architecture.
merged
Author avatar
PR by lalalune
vulkan: Qwen2.5-14B Q4_K_M bandwidth-efficiency cliff on Lunar Lake iGPU #7638
Technical audit of inference efficiency on modern Intel hardware, identifying kernel selection biases.
closed
Author avatar
Issue by NubsCarson

Summary

Overall Project Summary: May 20, 2026

On May 20, 2026, the elizaOS project successfully promoted the v2.0.2 release to `main` while significantly hardening cloud infrastructure by migrating agent lifecycle operations to a robust job queue system. The team also advanced the OWNER/AGENT connector registry architecture, enabling more granular identity management across plugins and the Eliza Cloud platform.

🚨 Needs Attention

  • elizaos/eliza#7836: Requires resolution regarding private key requirements to enable publishable Hyperliquid live harness runs.
  • elizaos/eliza#7837: Needs investigation into release orchestrator startup failures caused by missing platform-signing secrets during tag pushes.

✅ Completed Work

Cloud Infrastructure & Job Queue Migration * Decoupled core services from workers by migrating agent lifecycle operations (suspend, restart, snapshot, logs) to a job queue (elizaos/eliza#7810). * Refactored managed services to utilize asynchronous job enqueuing instead of inline shutdowns (elizaos/eliza#7815, elizaos/eliza#7816). * Improved cloud E2E mock stacks and frontend toast tracking for async job IDs (elizaos/eliza#7813, elizaos/eliza#7824, elizaos/eliza#7825).

Connector Registry & OAuth Enhancements * Implemented the OWNER+AGENT registry schema to support independent identities for users and agents (elizaos/eliza#7817). * Enabled end-to-end OWNER role support via Eliza Cloud OAuth and updated setup UI to be role-aware (elizaos/eliza#7819, elizaos/eliza#7851). * Removed hardcoded "OWNER" roles in OAuth callbacks for Linear, Calendly, and Shopify plugins (elizaos/eliza#7820).

Release Stabilization & UI Polish * Promoted `develop` to `main` for v2.0.2, including BSC wallet attachment fixes and performance optimizations (elizaos/eliza#7828, elizaos/eliza#7840, elizaos/eliza#7842). * Enhanced the elizaOS live demo and USB-installer workflows with mobile packaging and CI validation (elizaos/eliza#7803). * Improved UX by fixing UI z-index issues and making voice onboarding skippable (elizaos/eliza#7814, elizaos/eliza#7831).

🏗️ Work in Progress

New Pull Requests * elizaos/eliza#7871: Hardening USB persistence image flow. * elizaos/eliza#7850: Adding local voice and sandbox routing for mobile. * elizaos/eliza#7839: Sharing connector-accounts hook across OWNER+AGENT sections. * elizaos/eliza#7838: Implementing connector accounts schema and loader. * elizaos/eliza#7822: Refreshing bun lockfile for new workspaces.

🐞 Issue Triage

New Issues * elizaos/eliza#7836: Enable publishable Hyperliquid live harness runs. * elizaos/eliza#7837: Release orchestrator startup failure due to missing platform-signing secrets.

Full Stories

Story 1

A notable technical milestone was shared in the discussion channel where Shaw posted an image showcasing Eliza v3 running on ElizaOS (Linux) on an emulated RISC-V chip referred to as the Eliza E1.

Community member Zaday celebrated this achievement, describing it as ElizaOS Debian RISC-V 64-bit ISO successfully booting on the QEMU chip emulator in 35 seconds. This sparked curiosity about whether the team intends to develop their own dedicated chip for ElizaOS in the future.

Discord
Story 2

Regarding token strategy, a community member asked about a previously mentioned airdrop to ElizaOS holders, referencing either a Milady or Babylon related drop.

Shaw clarified that the Babylon airdrop did not happen due to running out of funds, and confirmed the team is now fully focused on ElizaOS. Zaday expressed strong support for this direction, advocating that the core team concentrate solely on the ElizaOS token and build multiple utility use cases for it similar to ETH or SOL, leaving new token creation to the broader market. Separately, a question arose about which Milady token receives buybacks from Milady app revenue, with Odilitime indicating it is the BNB version.

Discord
Story 3

In the coders channel, a full stack and AI developer introduced themselves and outlined their areas of interest including AI integrations, workflow automation, SaaS platforms, backend systems and APIs, AI agents and assistants, dashboards and analytics tools, and productivity and business-focused applications.

They expressed interest in connecting with founders and developers working on long-term projects. Additionally, in the general discussion channel, a developer announced the release of an Eliza plugin for DeFi agents on Base and Aave, published to NPM under the package name centinel-risk-protocol/eliza-plugin-centinel, offering real-time solvency scoring and flash-crash simulations, and invited community members to test it and provide feedback.

Discord