# Fact Briefing: 2026-01-26

## Overall Summary
The community is navigating technical advancements in MCP integration and V2.0.0 development alongside significant friction regarding ecosystem tokenomics and persistent security scams targeting token holders.

## Key Facts

- External MCP servers can be registered through the Eliza Cloud API using the POST /api/v1/mcps endpoint to enable agent proxy calls.
- ElizaOS has a $20M market cap with approximately 8 months of runway remaining as of January 24.
- The official Discord plugin was updated to version 1.3.8 to resolve audit log permission and private field access errors.
- The Hyperscape 'GOLD' token was clarified as a presale funding token rather than the main project token which will have fixed tokenomics.
- Hyperfy announced the shutdown of its legacy hosted platform hyperfy.io effectively April 1, 2026, transitioning to a self-hosted model.
- A fraudulent 'token migration' bot and technical support messages are targeting ai16z holders to solicit wallet addresses and tokens.
- Eliza V2.0.0 development is focused on a dynamic execution engine prototype and a Python-based bridge for expanded developer reach.

## Open Questions

- Does anyone know if all these tokens have any impact on ElizaOS or if they are fully independent?
- Is Twitter using shadcn on its web platform now?
- Why aren't there more specialized, single-purpose agents being deployed despite the framework's availability?

## Categories

### Twitter News Highlights
- Twitter web platform has transitioned to using the shadcn UI component library. (Sentiment: neutral)
- Consultant Vivek is assisting the team in obtaining an enterprise Twitter API key. (Sentiment: positive)

### GitHub Updates

#### New Issues/PRs
- [Pull_request #6384: V2.0.0: dynamic execution engine](https://github.com/elizaos/eliza/pull/6384) by odilitime - Status: open - Significance: Introduces schema-driven prompt execution and context validation to prevent LLM truncation.
- [Pull_request #6363: wasm agent runtime](https://github.com/elizaos/eliza/pull/6363) by revlentless - Status: open - Significance: Enables the Rust core to run in browser and Node.js environments via WebAssembly.
- [Issue #6364: Reflection evaluator fails with 'Entity not found'](https://github.com/elizaos/eliza/issues/6364) by thewoweffect - Status: closed - Significance: Critical fix for contact updates failing due to missing entity initialization.

#### Overall Focus
- Strategic focus on the V2.0.0 roadmap, including Rust-core WASM compatibility, Python bridges, and modularizing the SQL plugin adapter into domain-specific stores.

### Discord Updates
- **#coders:** Technical focus on MCP integration with Eliza Cloud and self-hosting strategies. Detailed API guidance provided for registering external servers. (Key Participants: SATA, SOLOMON VANDY, Odilitime)
- **#discussion:** Heavy debate regarding the 'GOLD' token launch for Hyperscape. Community expressed concern over liquidity management and developer wallet sizes. (Key Participants: shaw, DorianD, sayitaintso25)

### User Feedback
- Users suggest implementing an airdrop or token-pairing mechanism to link ecosystem projects back to the main $elizaos token value. (Sentiment: mixed)
- Inquiry regarding the lack of small, specialized 'one-trick pony' agents despite framework availability. (Sentiment: neutral)

### Strategic Insights

#### Ecosystem Funding Conflict
The team's reliance on new token launches to fund sub-projects (like Hyperscape) is creating a significant rift with holders who expect value accrual to the core token.

*Implications/Questions:*
  - Will the proposed network-level burn mechanism for game items satisfy investors?
  - Can the project sustain development with 8 months of runway without secondary launches?

#### Security and Support Automation
Malicious actors are successfully mimicking 'Support Bots' and ticket systems, indicating a need for verified, hard-coded UI elements for support within the Eliza Cloud platform.

*Implications/Questions:*
  - Should the team release a 'legitimacy toolkit' for community members to verify official bots?

### Market Analysis
- Core $elizaos project currently navigating a period of low market performance with only 4 'green days' in the last month. (Relevance: Drives community urgency for monetization strategies and Eliza Cloud launch.)