# Fact Briefing: 2026-01-30

## Overall Summary
The project is navigating a phase of architectural expansion through n8n workflow integration and AI routing frameworks, while simultaneously managing community tension regarding token distribution and ETH-chain liquidity issues.

## Key Facts

- A critical message ordering bug was identified in Eliza 1.7.2 where action callbacks execute in reverse order and omit structured return text.
- The core team is pivoting the architecture to integrate n8n workflow automation as the primary method for connecting services like Gmail and Notion.
- ElizaOS tokens on the ETH chain experienced a liquidity collapse resulting in 98% losses for users attempting to swap back to ETH/USDT.
- DorianD proposed 'ElizaRouter,' a distributed routing mechanism using small models like Phi-4 Mini and Mistral 7B to optimize model selection based on query complexity.
- The 'elizaos create' command failure was resolved by updating the CLI package to the scoped @elizaos/cli version and correcting documentation guides.
- A new 'Code Execution' plugin was launched, enabling AI agents to write and run code natively to solve problems.
- Token migration from ai16z to ElizaOS included a 1:10 supply increase, with 40% of the new supply allocated to the team.

## Open Questions

- Are the wallets holding 40% of the supply known and do they have a vesting schedule?
- Why did the team get 40% when it is open source after the 1:10 token increase?
- What existing frameworks are available for AI model routing based on prompt complexity?
- What small open-source models are best for routing decisions?
- Why are action callbacks in Eliza 1.7.2 executing in reverse order compared to documentation?

## Categories

### GitHub Updates

#### New Issues/PRs
- [Pull_request #6351: V2.0.0](https://github.com/elizaos/eliza/pull/6351) by lalalune - Status: open - Significance: Major structural overhaul removing non-essentials and focusing on Rust/TypeScript runtime.
- [Issue #6429: [Plugin] Integrate N8N Workflow Engine](https://github.com/elizaos/eliza/issues/6429) by borisudovicic - Status: open - Significance: Core strategic shift to use n8n for multi-service automation.
- [Issue #6388: Can not generate project](https://github.com/elizaos/eliza/issues/6388) by Abdulkader-Safi - Status: closed - Significance: Critical blocker for new developers that was fixed by scoping the CLI package.

#### Overall Focus
- Consolidating the framework into a service platform by stabilizing developer onboarding and expanding agent capabilities via n8n and code execution plugins.

### Discord Updates
- **#coders:** Technical focus on AI routing systems (ElizaRouter) and debugging callback sequence errors in version 1.7.2. (Key Participants: DorianD, Victor Creed)
- **#discussion:** High-intensity debate regarding tokenomics, specifically the 40% team allocation and the lack of liquidity on the ETH chain migration. (Key Participants: Odilitime, gby, Sarthak)
- **#core-devs:** Exploration of Composio for in-chat authentication and social media integration flows. (Key Participants: sam, Stan)

### User Feedback
- Community frustration over 98% value loss during ETH chain migration and lack of clear token utility beyond Jeju gas fees. (Sentiment: negative)
- Developers reported successful resolution of project generation errors after following updated CLI installation documentation. (Sentiment: positive)

### Strategic Insights

#### Shift to Workflow-First Architecture
By integrating n8n instead of building native plugins, the project accelerates its ability to connect with enterprise services like Gmail and Salesforce.

*Implications/Questions:*
  - Does this dependency on n8n impact the 'fully decentralized' goal for agents?
  - How will this affect the existing native plugin ecosystem?

### Market Analysis
- Market analysis predicts a bear market bottom within 6 months, with potential recovery beginning in 2027. (Relevance: Influences project runway planning and timing for upcoming product launches like Babylon and Hyperscape.)