# Fact Briefing: 2025-07-22

## Overall Summary
The project is shifting focus toward protocol-level tokenomics and core framework modernization following the V2 rollout. Major technical efforts include migrating from Node.js EventEmitter to Bun's native EventTarget for performance and standardizing service interfaces to improve modularity.

## Key Facts

- Kenk confirmed the development team is focusing on protocol-level tokenomics now that the V2 rollout is complete.
- A migration from Node.js EventEmitter to Bun's native EventTarget API was implemented across core APIs to improve performance.
- A new service architecture was introduced featuring a getServicesByType() method to allow plugins to depend on abstract services.
- Significant community concern was raised regarding the mint authority of AI16Z tokens and the lack of voting infrastructure to revoke it.
- The team reported that discussions with X regarding the suspension of the Eliza and Shawn accounts are moving in a positive direction.
- DorianD confirmed that the AI16Z smart contracts are currently not open source.
- Critical bug fixes were shipped for the CLI to prevent the incorrect inheritance of .elizadb directories in nested projects.
- A new plugin-quick-starter template was added to the CLI for streamlined backend-only plugin development.

## Open Questions

- What is the specific timeline for the resolution of the Twitter plugin 'Failed to fetch Home timeline' errors?
- How will custom plugin schema migrations be handled given the reported DatabaseMigrationService registration issues?

## Categories

### GitHub Updates

#### New Issues/PRs
- [Pull_request #5609: Migrate from EventEmitter to Bun native EventTarget API](https://github.com/elizaos/eliza/pull/5609) by wtfsayo - Status: merged - Significance: Significant core framework refactor to improve runtime performance and compatibility with Bun.
- [Pull_request #5565: Implement service types and standardized interfaces](https://github.com/elizaos/eliza/pull/5565) by wtfsayo - Status: merged - Significance: Introduces modularity by allowing plugins to depend on abstract service types.
- [Issue #38: Twitter plugin failed to fetch Home timeline](https://github.com/elizaos/eliza/issues/38) by Ovodo - Status: open - Significance: A persistent pain point for users of the Twitter integration.

#### Overall Focus
- Development is currently focused on strengthening project foundations, improving the CLI stability, and modernizing the core framework using Bun-native APIs.

### Discord Updates
- **discussion:** Debates occurred regarding token transparency and contract control, specifically focusing on mint authority and the non-open-source status of contracts. (Key Participants: DorianD, Kenk, ZzzzHodl)
- **tech-support:** Technical discussions centered on Ollama integration for plugin-knowledge, with community members contributing code branches to resolve loading issues. (Key Participants: starlord, sayonara)

### User Feedback
- Users expressed significant concern over the project's centralized control via token mint authority and requested better documentation on governance. (Sentiment: negative)

### Strategic Insights

#### Transition to Protocol-Level Governance
The move toward protocol-level tokenomics suggests an effort to decentralize and automate ecosystem incentives now that the core infrastructure is stable.

*Implications/Questions:*
  - Does the current lack of voting infrastructure present a risk to the upcoming tokenomics rollout?

#### Shift toward Bun-native optimization
The consistent migration to Bun-native APIs (EventTarget, Spawn) indicates a strategic long-term bet on Bun as the primary execution environment over Node.js.

### Market Analysis
- Community members highlighted that the project previously sustained a $2.4B valuation with the current token structure to alleviate supply concerns. (Relevance: Used to defend the current token architecture amidst supply expansion fears.)