# Fact Briefing: 2025-01-11

## Overall Summary
Across the AI16z/ElizaOS ecosystem, discussions were dominated by governance and reputation fallout related to AICC and uncertainty in tokenomics leadership, while engineering activity remained high with multiple new model providers, plugins, and bug fixes landing in the ElizaOS repository.

## Key Facts

- On 2025-01-10, several AI16z core team members (Markus, Ejaaz, Ropirito) shifted focus to AICC, and Jin stated he would lead tokenomics efforts if needed.
- Shaw stated he donated 50% of his AICC allocation to the AI16z DAO, airdropped approximately 20% to contributors, and used approximately 10% for LP; Jin stated he sent 50% of his AICC allocation to the DAO.
- AI16z tokenomics discussions described a planned launchpad similar to pump.fun using virtual liquidity and bonding, where the DAO would earn LP fees for token buybacks.
- The AI16z tokenomics channel recorded a debate on whether launchpad pools should use AI16Z or SOL as the base pair.
- ElizaOS added support for Mistral AI as a model provider via PR #2137.
- ElizaOS integrated a DeepSeek AI provider via PR #2067.
- ElizaOS added Text-to-Speech (TTS) support with over 15 languages via PR #2110.
- A new GitHub issue (#2164) reported a pnpm build error involving incompatible parameter types ('url' and 'request') on a fresh clone.
- The elizaOS Discord daily stats for 2025-01-10 recorded 7,474 messages from 658 users.
- In the 'spartan_holders' channel, members discussed that Skely (described as a core developer) sold all DegenAI tokens 18 days earlier.

## Open Questions

- Is there a plan to refactor the entire Eliza repository?
- What happened to the AI16z/SOL pair? Can't sell it in Orca or Raydium
- When will tokenomics be released?
- How do I implement RAG (Retrieval Augmented Generation) with periodic data feeds?
- How do I make my agent post images on Twitter?
- Can we get Matrica in this server? Most of the solana ecosystem uses them not collabland
- Was wondering if people will get airdrop of 420 tokens?
- Who is actually building the launchpad?

## Categories

### Twitter News Highlights
- DankVR compared the Eliza and BabyAGI GitHub repositories, stating Eliza shows more active development and production usage despite fewer stars. (Sentiment: neutral)
- DankVR highlighted an Eliza plugin for Obsidian that turns an Obsidian vault into an AI agent/portable second brain. (Sentiment: neutral)
- DankVR discussed using tokens for incentive alignment and mentioned agents analyzing contributions for retroactive public goods funding. (Sentiment: neutral)

### GitHub Updates

#### New Issues/PRs
- [Pull_request #2137: feat: Add Mistral AI as new model provider](https://github.com/elizaOS/eliza/pull/2137) by unknown - Status: merged - Significance: Adds an additional LLM provider option for ElizaOS agents.
- [Pull_request #2067: feat: Add DeepSeek AI provider support to Eliza](https://github.com/elizaOS/eliza/pull/2067) by unknown - Status: merged - Significance: Adds an OpenAI-compatible provider integration for DeepSeek.
- [Pull_request #2110: feat: TTS(Text2Speech) with over 15 languages support!](https://github.com/elizaOS/eliza/pull/2110) by unknown - Status: merged - Significance: Introduces multilingual TTS capability for voice experiences.
- [Pull_request #2141: feat: plugin-hyperliquid](https://github.com/elizaOS/eliza/pull/2141) by unknown - Status: merged - Significance: Adds Hyperliquid API interaction capability via a dedicated plugin.
- [Pull_request #2171: chore: Prep v0.1.8 (dev => main)](https://github.com/elizaOS/eliza/pull/2171) by unknown - Status: merged - Significance: Rolls development changes into main in preparation for a release.
- [Issue #2164: Type compatibility problems with parameters 'url' and 'request' when making a fresh clone](https://github.com/elizaOS/eliza/issues/2164) by unknown - Status: open - Significance: Reported build failure affecting fresh installs.
- [Issue #2158: Database connection error when using the image generation plugin](https://github.com/elizaOS/eliza/issues/2158) by unknown - Status: open - Significance: Reported crash related to image generation plugin database connectivity.
- [Issue #2161: Replies to TWITTER_TARGET_USER are sent twice when ElizaOS is restarted](https://github.com/elizaOS/eliza/issues/2161) by unknown - Status: open - Significance: Reported duplication bug in Twitter automation behavior after restart.

#### Overall Focus
- Development emphasized expanding model provider support (e.g., DeepSeek, Mistral), adding new Web3/plugins (e.g., Hyperliquid, Primus zkTLS, Quai), and improving stability via bug fixes, tests, and refactors.

### Discord Updates
- **#discussion:** Conversation focused on AI16z/AICC controversy and governance clarity (allocation concerns, leadership uncertainty), alongside ongoing ElizaOS technical questions and plans to automate summaries and communications. (Key Participants: Jin, Shaw, BOSSU, Smedroc)
- **#💻-coders:** Developer troubleshooting centered on Twitter client configuration (rate limits/post intervals), template overrides, cache issues, vector database integration for persistent memory, and patterns for action chaining with loop safeguards. (Key Participants: 0xLabsTheCoder, kobra, Neodotneo, BitBeard, cryptoAYA)
- **#tokenomics:** Tokenomics discussion centered on a pump.fun-like launchpad plan and debate over AI16Z vs SOL as base pair; Jin stated he would lead tokenomics if needed after shifts of focus to AICC by other contributors. (Key Participants: jin, plur_daddy, eskender.eth, DorianD)
- **#🥇-partners:** Partners discussed AICC advisory involvement and allocations; Shaw said he resigned as an advisor and described a policy that 'launching a memecoin = fired', while also describing ongoing tokenomics and trust marketplace work. (Key Participants: Shaw, Jin)
- **#spartan_holders:** DegenAI holders asked for clarity on development status, buybacks, and legitimacy; discussion noted Skely sold all tokens 18 days earlier and requested more transparency about the team and roadmap. (Key Participants: jin, DorianD)
- **#3d-ai-tv:** Work continued on the AI Podcast/3D AI TV project; FishAI was introduced as a modular Unity system enabling agent integration (scene generation, camera control, viewer interaction), with constraints on factual accuracy and avoiding exploitable speculation. (Key Participants: fishai, SM Sith Lord, boom)

### User Feedback
- Users raised concerns that the AICC token launch allocation favored insiders/KOLs and asked for clearer separation and guidelines between AI16z and related projects (AICC, Partners DAO). (Sentiment: negative)
- Multiple users reported the Twitter client not respecting post interval and rate limiting settings and requested clearer configuration documentation. (Sentiment: mixed)
- Community members requested a concrete AI16z token value accrual mechanism beyond 'through the DAO' and asked for more frequent tokenomics progress updates. (Sentiment: neutral)
- DegenAI holders requested official clarification on development status, buybacks, and whether DegenAI trading venues are legitimate given reports of limited sellability. (Sentiment: negative)
- Users discussed potential rebranding from 'ai16z' to 'Eliza Labs' for mainstream acceptance. (Sentiment: neutral)

### Strategic Insights

#### Parallel progress: governance turbulence alongside rapid shipping
Community attention is split between governance/reputation management (AICC allocations, leadership focus shifts) and continued rapid technical delivery (new providers, plugins, TTS, refactors).

*Implications/Questions:*
  - What minimum governance communications cadence would reduce repeated unanswered tokenomics questions?
  - Should contributor recognition and conflict-of-interest policies be formalized in a public document?

#### Developer experience bottlenecks around social clients
Recurring Discord support threads and GitHub issues focus on Twitter client reliability (rate limits, duplicate replies, parsing/formatting), suggesting social integrations are a major operational pain point for builders.

*Implications/Questions:*
  - Should Twitter client configuration be consolidated into a single canonical guide with validated examples?
  - Should automated regression tests be prioritized for social-client restart and deduplication behavior?

### Market Analysis
- AI16z launchpad discussions explicitly referenced pump.fun mechanics (virtual liquidity then bonding) and competing platforms such as Virtuals. (Relevance: Frames product positioning and competitive pressure for an agent/token launch platform.)
- A debate occurred on whether to use AI16Z or SOL as the base pair in launchpad pools, with liquidity vs. 'monetary premium' arguments discussed. (Relevance: Base-pair choice affects liquidity access, pricing mechanics, and token demand pathways.)
- On 2025-01-09, Shaw's joke tweet about leaving the project caused market panic before clarification. (Relevance: Shows sensitivity of market/community reactions to leadership communications.)