# Fact Briefing: 2026-03-18

## Overall Summary
Discussions centered on the ElizaOS v2.0.0 architecture and the upcoming elizacloud product launch, contrasted by significant community friction regarding token migration transparency and price performance.

## Key Facts

- Odilitime proposed shipping ElizaOS v2.0.0 with zero default skills to prevent framework bloat, favoring a decentralized discovery model via external skills.md files.
- The team scheduled the elizacloud product launch for the end of the current week or early next week to power the ElizaOS revenue flywheel.
- Developer dinesh integrated support for over 100 onchain data sources into the EVM plugin using goldrush.dev.
- A transparency gap was identified in the ai16z to elizaOS migration, with approximately 54% of the total supply reportedly unaccounted for.
- The x402Guard security infrastructure was introduced to provide per-step transaction evaluation and layered limit systems for DeFi agents.
- Community members reported an 'Invalid Dynamic Link' error in the Google Form-based role assignment system.
- A proposal was made to create a centralized directory for skills and plugins modeled after Clawhub.
- Effect AI proposed a native API integration to allow ElizaOS agents to outsource tasks to a decentralized human worker network.

## Open Questions

- Does Milady support Sol or BSC after all?
- What percentage of ai16z tokens actually migrated to elizaOS?
- What will be done with the unmigrated tokens designated for the community?
- Can I use Eliza to develop Solana dApps?
- Should we ship v2.0.0 with 0 skills and promote external skill hosting/discovery?
- Do you happen to have a ticket channel where I can talk to an admin?

## Categories

### GitHub Updates

#### New Issues/PRs
- [Pull_request #6597: v2.0.0 skills folder implementation](https://github.com/elizaos/eliza/pull/6597) by Odilitime - Status: open - Significance: Implements the core folder structure for the v2.0.0 skills architecture.
- [Pull_request #6509: Major database refactor](https://github.com/elizaos/eliza/pull/6509) by unknown - Status: open - Significance: Improves long-term system architecture and reliability.

#### Overall Focus
- Focus shifted toward a major beta release, prioritizing user onboarding, platform stability, and clearing functional blockers.
- Development of decentralized identity features via the SAID Protocol on Solana for verifiable agent actions.

### Discord Updates
- **#discussion:** Heavy debate regarding ELIZA token performance and the marketing strategy involving Shaw's promotion of Milady to drive elizacloud distribution. (Key Participants: Odilitime, lekt9, gby, Taco)
- **#coders:** Technical issues with role assignment forms and introduction of high-level AI/Full-stack developers to the community. (Key Participants: heimejorgen, truebrujah)
- **#xfn-framework:** Discussion on establishing a structured registry system for skills and plugins similar to Clawhub. (Key Participants: SYMBiEX, Stan)

### User Feedback
- Community frustration regarding the perceived lack of marketing and utility for the ELIZA token while competitors see growth. (Sentiment: negative)
- Requirement for enterprise-grade UI trust signals and RTL localization (Arabic) to move agents from 'demo magic' to production ready. (Sentiment: neutral)

### Strategic Insights

#### Decentralized Skill Discovery
Moving toward a zero-default-skill core for v2.0.0 shifts the discovery burden to the community and external domains.

*Implications/Questions:*
  - Will this decrease barrier to entry for new users or create fragmentation?
  - How will the 'official' registry interact with these decentralized domains?

#### Token Migration Transparency Risk
The high percentage of unmigrated tokens (est. 54%) creates a significant narrative risk and potential supply overhang concern.

*Implications/Questions:*
  - Does the team have a deadline for the migration window?
  - What is the plan for the uncollected original supply?

### Market Analysis
- ELIZA token price performance is lagging behind the broader AI crypto ecosystem pump. (Relevance: Drives community dissatisfaction and pressure on leadership for clearer utility roadmap.)