# Fact Briefing: 2026-02-23

## Overall Summary
elizaOS is undergoing a significant transition to v2.0.0, characterized by major database refactoring and the integration of on-chain identity via the SAID Protocol. Development focus has intensified on performance optimization and expanding the plugin ecosystem, including new tools for exchange listings and NFT capabilities.

## Key Facts

- Milady announced the AGENTS NFT drop (ERC-8004) across ETH, BSC, Base, and Solana, providing free mints for elizaOS holders.
- PR #6521 was submitted for elizaOS v2.0.0, removing 2,600 lines of code primarily to eliminate auto-migration from 1.4.x to 1.6.x.
- The SAID Protocol was integrated in PR #6510 to provide agents with verifiable on-chain digital identities on the Solana blockchain.
- Odilitime reported hitting 200k token limits regularly due to plugin density and initiated work to improve bootstrap providers and evaluations.
- The SolCex Exchange plugin (@buzzbd/plugin-solcex-bd) for v2.0.0 was published on npm, featuring a 100-point token scoring system.
- Core developers confirmed that v2.0.0 is the recommended branch, despite having less documentation than stable versions.
- The project clarified the ai16z token as deprecated following a 1:6 migration to the elizaOS ecosystem.
- ElizaCloud users identified critical UI bugs, including broken mousepad scrolling on the API explorer page and recurring API key errors.

## Open Questions

- Could this run again?
- Isn't the upgrade for $milady.ai not ElizaOS?
- Can we deploy dApps to Solana seeker?
- Is there still a live Eliza agent that can answer questions about the most recent ElizaOS codebase?
- Does 'use a different key' mean users can enter their own API keys (like OpenAI key for gpt-4o) similar to OpenRouter BYOK?
- For Milady, we have BNB and Solana - are both valid?

## Categories

### Twitter News Highlights
- Shaw shares AI and development updates exclusively on Twitter, while crypto content is posted to Farcaster. (Sentiment: neutral)

### GitHub Updates

#### New Issues/PRs
- [Pull_request #6521: align RLS isolation with v1 patterns](https://github.com/elizaos/eliza/pull/6521) by standujar - Status: open - Significance: Critical database maintenance for v2.0.0 that defines migration strategy and security protocols.
- [Pull_request #6510: add SAID Protocol on-chain Solana identity](https://github.com/elizaos/eliza/pull/6510) by kaiclawd - Status: open - Significance: Introduces verifiable decentralized identity for agents.
- [Issue #6486: URL in message triggers duplicate LLM calls](https://github.com/elizaos/eliza/issues/6486) by thewoweffect - Status: open - Significance: Major cost and performance bug leading to doubled token usage.

#### Overall Focus
- Development is centered on the transition to v2.0.0, involving significant code deletions of legacy migration paths and optimizing the runtime for multi-language support (Rust, Python, TS).

### Discord Updates
- **#core-devs:** Technical deep dive into the 'Great DB Refactor' and v2.0.0 migration strategy. Decision made to force users to move to 1.6.x before upgrading to v2.0.0. (Key Participants: standujar, odilitime)
- **#coders:** Announcement of the SolCex Exchange plugin and discussions on ERC-8004 NFT standard implementations on Base and Ethereum. (Key Participants: Ogie, jin)
- **#discussion:** Community showcase of versatile agents (Reservation, Travel, DB analysis) and clarification on the non-relationship between Spartan infrastructure and Milady wallet. (Key Participants: DarmaStef, Odilitime)

### User Feedback
- Users reported unusable scrolling on the ElizaCloud API explorer dashboard and errors when attempting to use the 'Send Request' test feature. (Sentiment: negative)
- Positive feedback regarding the Erlang-based 'unbreakable agents' code proposed for integration. (Sentiment: positive)

### Strategic Insights

#### v2.0.0 Documentation Gap
There is a temporary strategic tension between the stability of v1.x and the recommended adoption of v2.0.0, which currently lacks comprehensive documentation.

*Implications/Questions:*
  - Will the lack of documentation stifle the v2 beta onboarding?
  - How quickly can the documentation team sync with the v2.0.0 feature set?

#### Ecosystem Partner Sentiment
Weak communication has been identified as a source of negative sentiment among influential partner groups, coinciding with the restoration of key social media accounts.

*Implications/Questions:*
  - Should a dedicated partner-comms lead be appointed to manage influential groups?

### Market Analysis
- elizaOS market cap is approximately 10 million, significantly lower than its historical peak of nearly 3 billion. (Relevance: Reflects the transition from a hype-driven phase to an infrastructure-building phase.)