# Fact Briefing: 2025-01-05

## Overall Summary
ElizaOS maintained high development velocity with multiple new plugins and fixes landing (including a postinstall fix and Twitter-related improvements), while Discord discussions centered on recurring Twitter integration reliability issues and an active debate over single-pool vs two-pool tokenomics design for new agent launches.

## Key Facts

- On 2025-01-04, the elizaOS Discord logged 3,856 messages from 585 users.
- PR #1872 fixed the plugin-node postinstall script installation issue.
- PR #1861 added a Stargaze plugin to retrieve NFT information from the Cosmos marketplace.
- PR #1826 added a Cosmos plugin for blockchain interactions.
- Issue #1862 reported a security analysis finding critical issues with secret management in the codebase.
- The tokenomics channel discussed a proposal to use ai16z as the base asset for bonding curves via a single-pool model that includes a SOL/USDC-to-ai16z "zapping" mechanism.
- The 3d-ai-tv channel discussed using QuickTime Apple ProRes 4444 with alpha (rendered from a PNG sequence) for transparent overlays in video production.
- In the spartan_holders channel, jin reported training a LoRA model for DegenAI and optimizing it to under 6MB.
- The partners channel discussed a wallet that received 20M DegenAI tokens from a dev wallet and began selling them, with an explanation tied to a DAO payment negotiation.

## Open Questions

- How do I store input and memory in my agent?
- Is there any option to hardcode few answers?
- How do I see degenai trades?
- How do I provide a list of Twitter users to interact with in Character Files?
- Is there a way to force AI agent reply and content to always include some URL or certain content?
- Has anyone figured out how to utilize facts/goals?
- What is the most stable version of Eliza we should use?
- How often does the news aggregator update?
- Will partners get a heads up before tokenomics officially get launched/tweeted?
- Is the upcoming whitepaper this month going to include $degenai's whitepaper and tokenomics?
- What timeframe are we planning to launch the launchpad and see more of the tokenomics?
- Does anyone have the list of hackathon projects that's utilizing elizaOS?
- Is anyone working on defi functionality?

## Categories

### Twitter News Highlights
- @dankvr recommended @ardriveapp as an Arweave CLI tool and discussed using Ethereum meeting notes/forum content to create AI agents quickly. (Sentiment: neutral)
- @dankvr stated that @ai16retardedz are "grifters" and claimed there is no partnership, referencing a screenshot as evidence. (Sentiment: neutral)

### GitHub Updates

#### New Issues/PRs
- [Pull_request #1872: fix: Fix postinstall script](https://github.com/elizaOS/eliza/pull/1872) by unknown - Status: merged - Significance: Fixes installation failures caused by postinstall behavior in plugin-node.
- [Pull_request #1861: feat: Add Stargaze plugin](https://github.com/elizaOS/eliza/pull/1861) by unknown - Status: merged - Significance: Adds Cosmos NFT marketplace (Stargaze) integration capability.
- [Pull_request #1826: feat: add cosmos plugin](https://github.com/elizaOS/eliza/pull/1826) by unknown - Status: merged - Significance: Adds Cosmos chain interaction support.
- [Pull_request #1860: Feat: add infera as an inference provider](https://github.com/elizaOS/eliza/pull/1860) by inferanetwork - Status: merged - Significance: Adds a new inference provider option.
- [Issue #1862: security analysis report revealing critical issues with secret management](https://github.com/elizaOS/eliza/issues/1862) by unknown - Status: open - Significance: Tracks reported security and secret-management concerns.
- [Issue #1859: Generating new tweet issue](https://github.com/elizaOS/eliza/issues/1859) by unknown - Status: open - Significance: Tracks failures in tweet generation/posting.

#### Overall Focus
- Development focused on shipping new blockchain/NFT-related plugins (Stargaze, Cosmos) and stabilizing installation and Twitter-related behaviors (postinstall fix, Twitter profile caching improvements).

### Discord Updates
- **#discussion:** General discussion centered on agent building and operation (hosting options, API provider choices), alongside community interest in ai16z and exchange/listing speculation; multiple user questions about agent memory and hardcoded answers were asked without resolution in the channel summary. (Key Participants: YoungPhlo, jin, BOSSU)
- **#💻-coders:** Developers discussed build/runtime issues and integrations (Ollama/Anthropic/OpenAI, Twitter and Telegram), including a plugin-node postinstall problem and repeated Twitter behavior issues (auto replies/retweets, auth/shadow ban concerns). (Key Participants: Santi, Matt Gunnin, LiamVDB, SquintDev)
- **#tokenomics:** Participants debated a single-pool model using ai16z as the base asset for bonding curves (with SOL/USDC zap-to-ai16z) versus an earlier two-pool model (AT:SOL and AT:ai16z), and discussed plugin fee flexibility and buyback design (liquidity vs burning). (Key Participants: 563 blocmates, eskender.eth, Akin)
- **#🥇-partners:** Partners discussed Twitter account compliance steps (including adding "Parody"), an observed wallet selling 20M DegenAI tokens (explained as related to a DAO payment negotiation), tokenomics whitepaper timing, and ecosystem tracking via awesome-eliza. (Key Participants: jin, 0xwitch, shakejr)
- **#3d-ai-tv:** The team iterated on an AI-produced show pipeline (including "Clank Tank"), with work on a show runner that can generate new episodes or replay prior ones for testing; video production details included using ProRes 4444 with alpha for overlays and Unity transition work. (Key Participants: SM Sith Lord, boom, KamX)
- **#spartan_holders:** Discussion focused on DegenAI evolution (including a LoRA training update) and concepts for making the agent more interactive (3D trading floor, WebGL version) plus experimentation ideas like behavior-modifying mechanisms gated by NFTs. (Key Participants: jin, shaw, smetter)

### User Feedback
- Multiple users reported Twitter integration problems including authentication failures, rate limiting, duplicate replies, unwanted automatic replies/retweets, and potential shadow banning concerns. (Sentiment: negative)
- Users reported build and install errors tied to plugin-node and lockfile state, including Buffer/ArrayBuffer type mismatch reports and postinstall timing issues. (Sentiment: negative)
- A documentation navigation suggestion proposed replacing date-based doc filenames (YYYY-MM-DD) with descriptive filenames for easier browsing. (Sentiment: neutral)

### Strategic Insights

#### Tokenomics design is an active decision point
Community discussion contrasts a single-pool, ai16z-base bonding curve approach with a more complex two-pool design intended to maximize distribution and external liquidity, alongside open questions on plugin fee governance and buyback routing.

*Implications/Questions:*
  - Which pool model is preferred for launchpad simplicity vs long-term fee capture?
  - Should buybacks prioritize liquidity depth rather than burns in early ecosystem growth?

#### Operational reliability of Twitter client is a recurring friction point
Across multiple days of Discord discussion, Twitter issues recur (duplicates, response control, rate limiting/auth), and users seek configuration mechanisms (templates and env controls) to reduce unwanted behavior.

*Implications/Questions:*
  - Should the project prioritize a hardened Twitter behavior configuration surface (e.g., explicit toggles for actions) in core docs and defaults?

#### Media/AI show tooling is progressing in parallel with core framework work
The 3d-ai-tv workstream is building a show runner and Unity pipeline while asking for repeatable testing workflows (replay vs regenerate) and standardized media formats (alpha channel).

*Implications/Questions:*
  - What integration points (news aggregator, character profile system, asset pipeline) should be productized first?

### Market Analysis
- The community discussed a Bybit listing vote that reached 100% listing odds, with voting ending on Monday. (Relevance: Exchange-listing discussions can affect attention, onboarding demand, and support burden for new users.)
- DegenAI was discussed as being listed on Binance Alpha. (Relevance: Visibility/traffic increases can raise support load and amplify the need for clear product positioning.)
- A wallet receiving 20M DegenAI tokens from a dev wallet and selling was discussed in the partners channel. (Relevance: Large transfers/sales are a recurring community concern and can drive requests for clearer treasury/settlement communications.)