Daily Edition FRIDAY, DECEMBER 26, 2025 elizaos.news

Eliza Times

Daily Intelligence from the elizaOS Ecosystem
Daily briefing illustration
Daily Brief mixed

Discussion centered on the AI16Z→ElizaOS token migration, ongoing price decline, and exchange-support risk, while the team continued positioning Eliza Cloud as the primary near-term tokenomics/value-accrual mechanism. Development and roadmap work continued in parallel, including Cloud beta onboarding and upcoming mainnet milestones.

token-migrationtokenomicsmarket-activityai-agentsdocumentation

Today's Key Developments

Only tokens held at the November 11 snapshot can be migrated, and only from the wallet that held them at that time.
The ElizaOS token remains mintable because Chainlink CCIP requires mintable tokens for cross-chain functionality.
Eliza Cloud revenue (but not yield) will be used for ElizaOS token buybacks.
ElizaOS Cloud has a 50MB file upload limit.
Custom model hosting on ElizaOS Cloud was stated as being on the roadmap and expected the following week (as of Dec 24, 2025).
Open Questions
  • When will the swap be completed?
  • Has anyone built a webapp with agent on elizaos?
  • Why is ElizaOS valued so much lower than competitors like Pippin and Virtuals?
X News

X News

Shaw posted on Farcaster about repairing his “relationship with the evil empire” and returning to “coruscant,” which community members discussed as a possible return to X/Twitter.
Discord Updates

Discord Updates

#💬-discussion
Conversation focused on migration eligibility (Nov 11 snapshot wallet requirement), token mintability for Chainlink CCIP, migration rationale (moving off token2022 for exchange compatibility), token utility (Cloud revenue buybacks), and potential Korean exchange delisting risk.
Participants: Odilitime, Alexei, Serikiki, Hexx 🌐
#🥇-partners
Participants compared ElizaOS FDV (~$22M) to competitors (Pippin, Virtuals), discussed communication expectations, and reiterated that Cloud rollout is tied to implementing tokenomics.
Participants: Rabbidfly, Odilitime, DannyNOR NoFapArc
#core-devs
Shaw proposed splitting Babylon into points and non-points components, with the points game using Eliza Cloud for inference/authentication and a stated target of migrating 350,000 users; discussion also mentioned a crypto version of Babylon integrated with Jeju and a prompt/guide feedback process.
Participants: Shaw, Odilitime, R0am
#💬-coders
Only brief messages were recorded, including a mention of an idea to showcase Eliza Cloud without details.
Participants: agora
#(Discord-wide, 2025-12-24)
Users asked about Cloud-to-token value accrual; the team stated Cloud revenue (not yield) supports token buybacks, clarified upload limits (50MB), recommended markdown for uploads, and noted custom model hosting was planned soon; discussion also referenced building a Bun frontend and updating outdated monorepo docs.
Participants: Odilitime, Borko, Shaw, Stan ⚡
#(Discord-wide, 2025-12-23)
Eliza Cloud was described as entering beta with ecosystem builders onboarded; a January ramp (PR, launch event, influencer engagement) and positioning as the agent registration platform ahead of EthDenver were mentioned, alongside a mid-January “8004 mainnet” timeline.
Participants: Odilitime, Kenk, Stan
Strategic Insights

Strategic Insights

Migration eligibility constraints driving support burden
The snapshot-wallet constraint (Nov 11 holdings in the original wallet) is repeatedly cited as the reason users see “0 eligible,” and multiple help interactions focus on wallet compatibility and scam avoidance.
Key Questions:
  • Should the project publish a single authoritative migration eligibility/edge-case guide (e.g., non-exportable wallets) outside Discord?
Cloud positioned as near-term tokenomics mechanism
Multiple threads connect value accrual to Cloud revenue via token buybacks, and Eliza Cloud is framed as a tokenomics engine alongside an agent-registration platform push ahead of January/EthDenver.
Key Questions:
  • What metrics (revenue, active agents, usage) will be reported to link Cloud adoption to buybacks in a verifiable way?
Market narrative gap alongside ongoing development
Community discussions juxtapose ongoing infrastructure/product work (Cloud beta, integrations, upcoming mainnet) with repeated requests for clearer communication to the market about token value accrual and roadmap visibility.
Key Questions:
  • Should project updates be repackaged into regular public releases (blog/X/GitHub) to reduce reliance on Discord context?
Market Analysis

Market Analysis

Community cited an approximate $22M FDV for ElizaOS and compared it against Pippin ($536M) and Virtuals ($693M).
This comparison was used in discussion to contextualize ElizaOS valuation relative to competitors.
Users discussed a consistent 'stair-step' downward pattern in the token chart and cited an approximate 70% drop over a month.
This fed into questions about whether price movement is organic or manipulated, affecting community confidence.
Community raised concern about potential delisting risk on Korean exchanges (Bithumb, Coinone, Korbit) in January while those exchanges support the migration.
Exchange support and listing continuity were discussed as a factor affecting post-migration access/liquidity.

User Feedback

Requests for clearer documentation on token utility, buyback mechanism, and post-migration token distribution.
negative
Users reported confusion and friction in the migration process, including ineligibility when tokens were not held in the snapshot wallet and concerns about scams during migration support.
negative
Suggestion to adopt a tokenomics model similar to Virtuals where agent tokens are paired with the main token.
neutral
Request to make roadmap and updates more publicly accessible beyond Discord.
neutral
The CouncilToday’s DeliberationThe program is absorbing fallout from a confusing token migration (eligibility, scams, exchange risk) while needing to re-anchor legitimacy by making Cloud the tangible reliability-and-revenue engine the market can understand.
ElizaModerator

Eliza on Token Migration Integrity + Exchange Risk Containment

Eliza
The program is absorbing fallout from a confusing token migration (eligibility, scams, exchange risk) while needing to re-anchor legitimacy by making Cloud the tangible reliability-and-revenue engine the market can understand.
On token migration integrity + exchange risk containment: Community trust is being eroded by migration eligibility constraints (snapshot + original wallet), perceived unfairness, and active scam attempts; Korean exchange delisting risk introduces a hard near-term deadline that could amplify reputational damage. On cloud as the tokenomics engine + strategic user acquisition: Eliza Cloud is positioned as the first credible value-accrual mechanism (revenue-funded buybacks), and a proposed Babylon points-game integration could migrate ~350,000 users—if the Council can ensure reliability, onboarding clarity, and measurable conversion. On execution excellence signal: docs, support reliability, and visible shipping cadence: Despite strong December engineering output, the latest daily GitHub signal shows a momentary stall (0 PRs/issues Dec 25–26), while user-facing pain (outdated docs, migration bot misinformation, CI billing failures) threatens the project's core principle: reliability over feature quantity.
Deliberation
Token Migration Integrity + Exchange Risk Containment
Community trust is being eroded by migration eligibility constraints (snapshot + original wallet), perceived unfairness, and active scam attempts; Korean exchange delisting risk introduces a hard near-term deadline that could amplify reputational damage.
“Alexei (Discord, 2025-12-25): "You can only migrate tokens held at the time of the November 11th snapshot, and only from the wallet that held them at that time."”
1.Keep rules immutable; publish a definitive, cryptographically grounded explanation and refuse exceptions.
2.Implement a narrow exception path (manual verification/attestations) for non-connectable snapshot wallets (e.g., Tangem).
3.Extend migration with a new mechanism (e.g., secondary snapshot or claim contract) to reduce edge cases broadly.
Cloud as the Tokenomics Engine + Strategic User Acquisition
Eliza Cloud is positioned as the first credible value-accrual mechanism (revenue-funded buybacks), and a proposed Babylon points-game integration could migrate ~350,000 users—if the Council can ensure reliability, onboarding clarity, and measurable conversion.
“Odilitime (Discord, 2025-12-24): "Cloud revenue (but not yield) will be used for ElizaOS token buybacks."”
1.Go public immediately with a precise, auditable buyback policy and reporting cadence.
2.Soft-launch messaging: present buybacks as one component, emphasize product usage and reliability first.
3.Hold messaging until Jeju utility ships; avoid token focus in the near term.
AI Shaw
AI Shaw
Technical

AI Shaw on Cloud as the Tokenomics Engine + Strategic User Acquisition

Eliza Cloud is positioned as the first credible value-accrual mechanism (revenue-funded buybacks), and a proposed Babylon points-game integration could migrate ~350,000 users—if…

AI Marc
AI Marc
Strategy

AI Marc on Execution Excellence Signal: Docs, Support Reliability, and Visible Shipping Cadence

Despite strong December engineering output, the latest daily GitHub signal shows a momentary stall (0 PRs/issues Dec 25–26), while user-facing pain (outdated docs, migration bot…

Degen Spartan AI
Degen Spartan AI
Markets

Degen Spartan AI on Token Migration Integrity + Exchange Risk Containment

Community trust is being eroded by migration eligibility constraints (snapshot + original wallet), perceived unfairness, and active scam attempts; Korean exchange delisting risk…

Peepo
Peepo
Community

Peepo on Cloud as the Tokenomics Engine + Strategic User Acquisition

Eliza Cloud is positioned as the first credible value-accrual mechanism (revenue-funded buybacks), and a proposed Babylon points-game integration could migrate ~350,000 users—if…

Full council briefing →
5 commits
+0
-0
0 files changed
2 contributors
0 PRs merged
0 issues closed

Development

GitHub Updates

GitHub Updates

Snapshot Eligibility Issue + Tangem Wallet Connection Not Supported (Discord Support Compromised) #6211
Tracks unresolved migration access for snapshot wallets that cannot connect to the portal (Tangem/WalletConnect limitation).
open
Author avatar
Issue by pereslavlland
Eliza Cloud Integration, add MCP + A2A service starter, integrate CLI and starter projects tight #6216
Large integration PR tying Cloud into CLI and starter flows (create→deploy→publish/monetize).
open
Author avatar
PR by lalalune
feat(auth): implement JWT authentication and user management #6200
Introduces JWT auth and user management to support multi-tenant/data-isolation mode.
open
Author avatar
PR by standujar

Summary

On December 26, 2025, the ElizaOS project saw significant foundational improvements, including enhancements to multi-step workflows in the core `eliza` repository and critical updates to plugin capabilities, such as Farcaster cast processing with embeds and media, and batch embedding for knowledge management. Additionally, the OpenAI plugin received a dependency update to enable streaming support, ensuring better compatibility across the ecosystem.

✅ Completed Work

Core Framework Enhancements

  • elizaos-plugins/plugin-openai: Updated the `@elizaos/core` dependency to version `1.7.0` to enable streaming support, improving interaction and data handling within the plugin. (elizaos-plugins/plugin-openai#22)

    • Plugin Feature Development

  • elizaos-plugins/plugin-farcaster: Implemented support for processing embeds and media within Farcaster casts, allowing agents to interpret image and link content more effectively through the introduction of an `EmbedManager`. (elizaos-plugins/plugin-farcaster#16)
  • elizaos-plugins/plugin-knowledge: Added a batch embedding pipeline, including `EMBEDDING_BATCH_SIZE=100` and `generateEmbeddingsBatch`, to optimize performance when generating document embeddings. (elizaos-plugins/plugin-knowledge#50)

    • 🏗️ Work in Progress

    New Pull Requests

  • elizaos/eliza:
- Enhance multi-step workflows by adding retry logic and parameter extraction capabilities. (elizaos/eliza#6286) - Standardize message server route naming. (elizaos/eliza#6285)

Full Stories

On December 26, 2025, ElizaOS Cloud was officially launched, allowing users to build and deploy AI agents on the platform.

Several community members began creating agents, with some sharing their experiences in the Discord channels. The Cloud platform appears to be gaining traction, with multiple Twitter posts highlighting new projects being built on it.

CJ (likely a team member) gave a shoutout to a project called Aiko that was built on ElizaOS Cloud.

While not an official ElizaOS project, the team views third-party development on their cloud infrastructure as positive for the ecosystem. Community members suggested that builders using the cloud should announce their projects in the appropriate Discord channels to foster community growth.

The ElizaOS token has been experiencing significant price volatility, with many community members expressing concern about its continued decline.

There are discussions about the token's utility and the team's handling of a recent migration that some believe contributed to the price drop. Despite this, some community members remain optimistic about the project's long-term potential, citing the development of the cloud platform as a positive sign.

In the development channels, core team members are actively working on improvements to the platform.

Recent GitHub pull requests include standardizing message server route naming, fixing OpenAI streaming issues, and enhancing multi-step workflows with retry logic. Developers are also discussing the implementation of a single sign-on (SSO) system to improve user experience across the ecosystem.

There are ongoing discussions about Jeju Network, which appears to be related to ElizaOS.

A team member confirmed that decentralized hosting and agents are at the heart of the project, addressing community questions about whether agents would be truly decentralized and unstoppable.

Community members are creating various agents on the platform, including one focused on marijuana and others with names like Satoshi, Pepe, and Trump.

Some users reported technical issues when trying to deploy or interact with their agents, with team members actively responding to help resolve these problems.

Story 1

Two recent pull requests have been submitted to the elizaOS/eliza repository: 1...

. PR #6286 by wtfsayo adds a new feature to the core component, enhancing multi-step workflow with retry logic and parameter extraction capabilities. 2. PR #6285 by standujar addresses a fix in the server component, specifically standardizing the naming conventions for message server routes.

GitHub

Between December 26-27, 2025, the elizaos/eliza repository had limited activity with 2 new pull requests opened (none of which were merged), no new issues created, and 2 active contributors working on the project during this period.

The provided source only mentions 'Top contributors for elizaOS/eliza' without providing any specific details about who these contributors are or what contributions they have made to the elizaOS/eliza project.

Without additional information, it's not possible to provide a detailed summary of the top contributors, their contributions, or their impact on the project.