# Fact Briefing: 2025-09-23

## Overall Summary
The community focus centeres on the announced token migration from AI16Z to $elizaOS and the discontinuation of the Auto.Fun project. Technical efforts are currently prioritizing a critical Zod dependency conflict and architectural shifts toward decentralizing core components via neural networks.

## Key Facts

- A token migration from AI16Z to $elizaOS was announced following a significant price drop.
- The Auto.Fun project has been officially sunset and discontinued according to project lead Eric Chen.
- PR #5994 was opened by 0xbbjoker to resolve a Zod v3/v4 dependency conflict causing CI failures in plugin-knowledge.
- DegenAI staging version is scheduled for a minor update within two weeks.
- PR #5987 was merged to standardize the PGLite data directory environment variable in plugin-sql.
- ElizaOS core developers are exploring a browser end-to-end demo involving plugin-openai and plugin-sql.
- A security alert was issued by Jin regarding phishing scams targeting Gitcoin and GitHub users.

## Open Questions

- How will the closure of Auto Fun affect ELI5?
- Are you guys also sunsetting your incubator, Eli5 or is this completely separate from auto.fun?
- So this means leveraged positions that are currently in loss are fucked, correct?
- Will tokens in limit orders on Jupiter at prices higher than current price be included in the snapshot?
- How will users who are providing liquidity in raydium/dlmm etc be included?
- if i was going to use an old gemini version would i put that in the .env or in the character.json
- Why isn't each package isolated [regarding dependencies]?

## Categories

### GitHub Updates

#### New Issues/PRs
- [Pull_request #5994: chore: update zod pckg version](https://github.com/elizaOS/eliza/pull/5994) by 0xbbjoker - Status: open - Significance: Resolves a critical dependency conflict between AI SDK and Zod v3/v4 that is breaking CI.
- [Pull_request #5987: fix(plugin-sql): standardize PGLite data directory environment variable](https://github.com/elizaOS/eliza/pull/5987) by wtfsayo - Status: merged - Significance: Unified inconsistent environment variable naming for PGLite data storage.
- [Pull_request #5993: fix(build): improve TypeScript declaration generation and formatting](https://github.com/elizaOS/eliza/pull/5993) by wtfsayo - Status: merged - Significance: Addresses build configuration issues to ensure reliable .d.ts generation.

#### Overall Focus
- Development is centered on build system stability, TypeScript declaration reliability, and resolving dependency conflicts introduced by upstream SDK updates.

### Discord Updates
- **#discussion:** Heavy debate regarding the AI16Z to $elizaOS token migration and community concerns over liquidity/leverage holders. (Key Participants: DorianD, 0xfreedom, guilhermehelbig)
- **#core-devs:** Technical troubleshooting of CI failures caused by Zod v4 requirements in the newer AI SDK; discussion on package isolation. (Key Participants: 0xbbjoker, sayonara, Odilitime)
- **#partners:** Architectural proposals to move ElizaOS core code into neural networks running on P2P blockchain networks. (Key Participants: DorianD, Odilitime)

### User Feedback
- Users expressed frustration regarding DegenAI remaining in 'beta' for nearly a year without major updates. (Sentiment: negative)
- Community members highlighted a lack of transparency and negative management sentiment following the Auto.Fun closure. (Sentiment: negative)

### Strategic Insights

#### Core Tokenomics Pivot
The migration from AI16Z to $elizaOS represents a fundamental shift in the project's branding and economic structure, likely aimed at distancing from recent price volatility but creating short-term community friction.

*Implications/Questions:*
  - Does this migration plan account for complex DeFi positions like DLMM or limit orders?
  - How will this affect the 'generative token network' roadmap?

#### Decentralized Infrastructure Transition
There is a growing push toward replacing hard-coded logic with neural networks (Tesla-inspired model) to allow users to contribute to a P2P network from home.

*Implications/Questions:*
  - Is verifiable AI execution without TEEs technologically mature enough for this transition?

### Market Analysis
- Significant price drop in AI16Z followed immediately by a token migration announcement. (Relevance: Directly impacts community trust and creates urgency for clear migration documentation.)