# Fact Briefing: 2025-01-12

## Overall Summary
Development centered on stabilizing and expanding ElizaOS around the v0.1.8 release, with many new plugins/providers and multiple fixes for Twitter, database adapters (PostgreSQL/Supabase), and installation. Community discussions focused on launchpad/tokenomics design (including the 10% tribute model and base-pair debate), alongside trust/communications concerns related to AICC and DegenAI.

## Key Facts

- ElizaOS v0.1.8 was released and shared in Discord by Odilitime.
- ElizaOS added DeepSeek AI provider support (PR #2067) and Mistral AI model provider support (PR #2137).
- A fix was merged to adjust the Twitter plugin prompt to ensure JSON returns (PR #2196).
- A fix was merged for PostgreSQL RAG knowledge support (PR #2153) and a separate fix addressed Postgres adapter migration extension creation (PR #2188).
- The daily GitHub update for Jan 12, 2025 notes new issues including Echochambers plugin missing package (#2209) and pnpm outdated lockfile errors (#2215).
- Discord users reported recurring Twitter integration problems including authentication failures and rate limiting.
- Discord users reported Windows build problems for the latest ElizaOS version and noted WSL works better for some setups.
- DankVR stated he sent 50% of his AICC tokens to the AI16Z DAO and described AI16z DAO as a fair launch on DAOs.fun.
- In the tokenomics channel, members discussed a Q1 launchpad plan and debated whether ai16z or SOL should be the base pair for launchpad liquidity pools.
- In the spartan_holders channel, community members stated Skely (described as a core developer) sold all his DegenAI tokens roughly 18 days earlier.

## Open Questions

- What is the best UI for Eliza?
- When will tokenomics be announced?
- Will there be another hackathon?
- How do I fix the "TypeError: The database connection is not open" error?
- Is there an ongoing list/directory of agents being built on Eliza? (beyond pointers provided)
- Does this use elizaOS? (re: a referenced project/site)
- Is the game not playable yet on the website (only character selection visible), is that right?
- Did you literally use Stanford Ville's paper image without citing it?
- How come only 3 tokens are listed on elizas.world?
- Why did Skely sell all the degenai tokens?
- Is the team still trustworthy? (re: DegenAI)
- Who is working on degenai?
- What is the current progress of the tokenomics whitepaper?
- Has there been an analysis on hosting costs for agents?
- Will the launchpad shoulder hosting costs or will creators pay it?

## Categories

### Twitter News Highlights
- DankVR described AI16z DAO as a fair launch on DAOs.fun and highlighted ongoing livestreaming/education attracting teams and contributors. (Sentiment: positive)
- DankVR stated he sent 50% of his AICC tokens to the AI16Z DAO, describing it as directly benefiting all holders. (Sentiment: neutral)
- DankVR mentioned DAOs.fun working on "vested party list rounds" and automation for gathering/sharing updates to improve coordination. (Sentiment: neutral)

### GitHub Updates

#### New Issues/PRs
- [Pull_request #1184: feat: Integrate Livepeer LLM provider (o1 noted separately in recent PRs list)](https://github.com/elizaOS/eliza/pull/1184) by unknown - Status: open - Significance: Adds o1 integration (noted in daily summary as a significant PR).
- [Pull_request #2171: chore: Prep v0.1.8 (dev => main)](https://github.com/elizaOS/eliza/pull/2171) by odilitime - Status: merged - Significance: Release preparation for v0.1.8.
- [Pull_request #2196: fix(plugin-twitter): change prompt to ensure it returns json](https://github.com/elizaOS/eliza/pull/2196) by unknown - Status: merged - Significance: Addresses Twitter bot output formatting expectations (JSON return).
- [Pull_request #2153: fix: Koloxarto/fix ragknowledge for postgres](https://github.com/elizaOS/eliza/pull/2153) by unknown - Status: merged - Significance: Fixes RAG knowledge handling for PostgreSQL.
- [Pull_request #2188: fix postgres adapter migration extension creation which already exists at this point](https://github.com/elizaOS/eliza/pull/2188) by web3gh - Status: merged - Significance: Fixes PostgreSQL adapter migration behavior.
- [Issue #2209: Echochambers plugin not functioning correctly (missing package)](https://github.com/elizaOS/eliza/issues/2209) by unknown - Status: open - Significance: Reported plugin failure due to missing dependency.
- [Issue #2215: pnpm outdated lockfile errors complicating installation](https://github.com/elizaOS/eliza/issues/2215) by unknown - Status: open - Significance: Installation blocker affecting users with pnpm lockfile mismatches.
- [Issue #2210: Reorganize README files into a dedicated docs folder](https://github.com/elizaOS/eliza/issues/2210) by unknown - Status: open - Significance: Documentation structure request to improve navigation.
- [Issue #2200: Add support for custom S3 endpoints in plugin-node](https://github.com/elizaOS/eliza/issues/2200) by unknown - Status: open - Significance: Feature request to broaden S3 compatibility (e.g., non-AWS providers).

#### Overall Focus
- GitHub activity emphasized plugin expansion (e.g., NFT plugin, WhatsApp tests) alongside bug fixes for Twitter behavior and database adapters, plus documentation translations and maintenance (linting/renames).

### Discord Updates
- **#discussion:** Discussion noted the ElizaOS v0.1.8 release, new Ollama/DeepSeek integration mentions, ongoing Q1 launchpad planning, and community concerns about tokenomics communication and leadership clarity. (Key Participants: Odilitime, jin, MrBigTimeKing)
- **#💻-coders:** Coders focused on Twitter integration reliability (auth, rate limiting, formatting), Windows build issues (WSL suggested), and database adapter problems (Supabase/PostgreSQL) affecting RAG and image generation workflows. (Key Participants: masterdai, Apeguru, koloxarto, quixotechdon)
- **#tokenomics:** Tokenomics discussion centered on the 10% tribute model and launchpad design (pump.fun-like mechanics), including debate on whether ai16z or SOL should be the base pair for launchpad liquidity pools and how tributes should be used (e.g., LP creation). (Key Participants: jin, plur_daddy, eskender.eth, DorianD)
- **#spartan_holders:** Channel discussion included claims that Skely sold all DegenAI tokens ~18 days earlier and repeated requests for development status, roadmap clarity, and transparency on trading performance. (Key Participants: jin, Odilitime)
- **#3d-ai-tv:** Work continued on an AI show/podcast pipeline in Unity (camera angles, transitions, continuity via config files), with emphasis on content constraints (avoid endorsements/inaccuracies) and requests to expand the news aggregator to include social posts. (Key Participants: boom, SM Sith Lord, fishai)
- **#AI16z Ecosystem & Governance (general):** Governance discussion included leadership uncertainty as contributors shifted focus to AICC, controversy around AICC allocations, and statements that Shaw resigned as an advisor to AICC and discussed a policy of firing staff who launch memecoins. (Key Participants: Shaw, jin)

### User Feedback
- Users reported difficulties building the latest version on Windows and suggested WSL as a workaround. (Sentiment: negative)
- Users reported Twitter integration failures including authentication problems and rate limiting, and requested official Twitter API support with developer keys. (Sentiment: negative)
- Multiple discussions requested clearer tokenomics documentation and timelines, including a roadmap and a concise token value-proposition one-pager. (Sentiment: mixed)
- Users reported recurring database adapter issues (Supabase/PostgreSQL) impacting RAG and memory/knowledge workflows and requested better RAG documentation. (Sentiment: negative)
- In ideas-feedback-rants, users asked for clarification on whether a referenced website/game is playable and raised a citation concern about Stanford Ville imagery. (Sentiment: neutral)

### Strategic Insights

#### Launchpad + tribute model requires implementation clarity
Launchpad design discussions repeatedly return to enforceability (automatic tribute on-platform vs unenforceable off-platform) and capital formation choices (ai16z vs SOL base pair), implying the need for explicit product constraints and an implementation roadmap.

*Implications/Questions:*
  - What enforcement and incentive mechanisms exist for projects launching outside the platform?
  - Should the launchpad prioritize liquidity depth (SOL base) or token-centric value accrual (ai16z base)?

#### Reliability blockers concentrate around Twitter and data adapters
Across both Discord and GitHub, recurring operational friction clusters around Twitter authentication/rate limiting and database adapter behavior (Supabase/Postgres), suggesting these are key adoption bottlenecks for agent deployments.

*Implications/Questions:*
  - Should the project prioritize an official Twitter API path and a hardened adapter test matrix before additional integrations?

### Market Analysis
- Launchpad discussions referenced pump.fun’s model (bonding curve distribution and LP creation at completion) as a template for AI16z’s planned Q1 launchpad mechanics. (Relevance: Defines the likely liquidity-seeding mechanism and fee/LP flows for ecosystem launches.)
- Community debated whether ai16z or SOL should be used as the base pair for launchpad liquidity pools. (Relevance: Base-pair selection impacts launch friction, liquidity depth, and token-centric value accrual narratives.)
- Discord governance discussions included reputational concerns tied to AICC’s token launch allocations and leadership focus shifts. (Relevance: Community trust and contributor alignment can affect ecosystem growth and partner onboarding.)
- DegenAI holder discussions referenced a claimed developer token sell-off and requested transparency and roadmap updates. (Relevance: Token-holder confidence and communication cadence can influence partner participation and ecosystem stability.)