# Fact Briefing: 2026-01-09

## Overall Summary
ElizaOS faces a regulatory crisis as major Korean exchanges announce token delistings, while the development team prepares for a massive architectural shift with the Eliza 2.0 multi-language runtime proposal.

## Key Facts

- Korean exchanges Bithumb, Coinone, and Korbit announced token delisting for ai16z and elizaOS between February 9-12, 2026.
- DAXA coordinated the delisting decision citing a lack of transparency in the token migration process and failure to disclose material information.
- Shaw proposed Eliza 2.0 featuring a multi-language runtime in TypeScript, Rust, and Python with FFI plugin interoperability.
- The plugin-twitter repository implemented OAuth2 PKCE authentication for enhanced security.
- Korbit officially announced trading termination for the tokens on February 12, 2026.
- A hot reload functionality was implemented for backend development to automatically rebuild the CLI and restart the server.
- The plugin-sql package was updated to include Neon serverless database support and enhanced Row-Level Security.
- Bithumb confirmed it will support the AI16Z to ELIZAOS token swap despite the delisting announcement.
- PR #6333 was identified as a critical fix for compatibility issues between ElizaOS v1.7.0 and Discord plugin 1.3.3.

## Open Questions

- If I want to use eliza for X, helping me to find stuff on x do I need to pay for x API or does eliza have something to help/scrap this without needing to pay 200$ month?
- Do you need twitter api to use eliza to run a twitter agent?
- Why can't I migrate my old ai16z tokens purchased before November 2025?
- Has anyone played coding with minimax m2 here?

## Categories

### Twitter News Highlights
- Space event announced with Solana Foundation, PayAI, and Quantu for January 13th to discuss the 8004 protocol. (Sentiment: positive)

### GitHub Updates

#### New Issues/PRs
- [Pull_request #6351: V2.0.0](https://github.com/elizaos/eliza/pull/6351) by lalalune - Status: open - Significance: Major architectural overhaul focusing on a multi-language runtime and removing non-essentials.
- [Pull_request #6333: fix: plugin-bootstrap (+ sql minor) actions/providers for serverId => messageServerId change](https://github.com/elizaos/eliza/pull/6333) by odilitime - Status: merged - Significance: Critical fix for compatibility issues between core v1.7.0 and the Discord plugin.

#### Overall Focus
- Development is centered on core infrastructure stabilization, database security (RLS), and preparing for the V2.0.0 transition.

### Discord Updates
- **#discussion:** Heavy focus on the Korean exchange delisting crisis and technical issues regarding the AI16Z token migration eligibility. (Key Participants: Skullcross, 주니, stoikol, Hexx)
- **#core-devs:** Discussions on Eliza 2.0 architecture, interoperability through plugin-to-skill conversion, and optimizing workflow orchestration. (Key Participants: shaw, jin, R0am | tip.md, Stan)

### User Feedback
- Users are reporting significant confusion and technical failures in the token migration process, including 'max amount reached' errors and inability to see eligible tokens. (Sentiment: negative)
- Community concern regarding the lack of defined utility for the elizaOS token beyond rewards and its absence from payment/gas fee use cases. (Sentiment: neutral)

### Strategic Insights

#### Regulatory Sensitivity in East Asia
The coordinated delisting by Korean exchanges highlights a critical need for transparent material disclosure during project rebranding and migration phases to maintain exchange relationships.

*Implications/Questions:*
  - How can the project regain trust with regulatory bodies in highly active markets like Korea?

#### Architectural Interoperability
The move toward 'skills' rather than just 'plugins' signifies a shift to make ElizaOS components compatible with broader industry agent frameworks.

*Implications/Questions:*
  - Will the standardization of skills dilute the unique advantages of the ElizaOS plugin system?

### Market Analysis
- Termination of support on Korbit and Coinone creates a liquidity bottleneck for Korean investors despite Bithumb supporting the swap. (Relevance: Significant for token price stability and regional community engagement.)