Daily Edition THURSDAY, JANUARY 8, 2026 elizaos.news

Eliza Times

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

The ElizaOS ecosystem is managing critical version 1.7.0 compatibility issues with the Discord plugin while facing significant delisting actions from major Korean exchanges. Development has pivoted towards architectural scaling via event pumps and a decentralized marketplace called Bazaar on the Jeju Layer 2.

ux-improvementperformancemarket-activitypluginsinfrastructure

Today's Key Developments

Korean exchanges Bithumb, Coinone, and Korbit announced the termination of AI16Z/ElizaOS trading support between February 9-12, 2026.
Compatibility issues exist between ElizaOS version 1.7.0 and Discord plugin 1.3.3 due to a transition from serverId to messageServerId.
A fix branch (odi-17) was created on GitHub to address bootstrap actions and providers compatibility.
Bithumb confirmed it will support the AI16Z to ElizaOS token swap despite the delisting announcement.
The Bazaar decentralized marketplace was announced for agents running on the Jeju Layer 2.
Open Questions
  • When is the ElizaOS token getting utility within the ecosystem?
  • Why increase supply if the token isn't used as utility in the framework?
  • Do I need to pay for X API to use Eliza for finding stuff on X, or does Eliza have scraping alternatives?
  • How long does it take to get a response from the team on migration tickets?

Daily AI News

Tips & Techniques

  • Claude Code Planning Strategy: Structure conversations around single objectives per thread, plan until ambiguity disappears, then execute. Treat context like a budget and offload research to subagents to prevent performance degradation over long sessions. link
  • Memory Compression for RAG: PISCO compresses 128-token chunks into 8 special embeddings (16x reduction) without supervision, enabling 4-5x faster inference and 4x larger batch sizes while maintaining answer quality. link
  • AI Coding Metrics that Matter: Stop measuring lines changed. Instead track time from idea to working feature, bugs per release, and confidence when touching unfamiliar code—where AI actually shines. link
  • Verification Culture as Multiplier: Teams with solid verification practices (automated + human-driven) treat AI as an accelerator; teams without feel chaos multipliers. The difference is *who* verifies *what* and *when*. link

New Tools & Releases

  • UniVideo: Unified framework for video understanding, generation, and editing in one model. Demonstrates cross-domain generalization (editing transfers from image data) and compositional task generalization (unseen task combinations). link
  • Boltz PBC Launch: Open-source AI models for protein and small-molecule design. Launched as Public Benefit Corporation with $28M seed; accessible via web platform for scientists without computational expertise. Partnership with Pfizer announced. link
  • Qwen3-VL-Embedding & Qwen3-VL-Reranker: New multimodal retrieval and cross-modal ranking capabilities advancing state-of-art. link
  • GRPO Fine-tuning on T4 GPUs: Memory-optimized GRPO reduces 7B model VRAM usage to 9.2GB (~7x reduction), making large model fine-tuning accessible on consumer hardware via free Colab. link

Research & Papers

  • Epiplexity vs Entropy: New framework rethinking information theory for computationally bounded intelligence. Suggests current complexity measures miss what matters for practical AI systems. link
  • Hyperparameter Transfer Mechanisms: When and why hyperparameter transfer works in practice. Includes conjecture backed by extensive experiments explaining fast transfer phenomena. link
  • LLM Book Memorization at Scale: Production LLMs leak near-exact book text; Claude 3.7 Sonnet hits 95.8%. Raises serious questions about training data and evaluation. link

Industry News

  • Infosys Partners with Cognition AI: Major outsourcing firm backing AI software engineers signals shift in enterprise AI deployment strategy. link
  • Tailwind CSS Downsizing: 75% staff reduction tied to AI agents generating CSS, illustrating real disruption to template-based business models. The real issue: when you have an interpolation machine, selling templates becomes unviable. link
  • Memory Infrastructure Thesis: HBM/DRAM/Flash constraints are the real bottleneck, not chips. Major cloud providers asking Micron for open-ended orders at any price—supply crisis beyond 2026. link

--- *Curated from 600+ tweets*

Discord Updates

Discord Updates

#discussion
Heavy focus on addressing Discord bot 'No server ID found' errors and reacting to Korean exchange delistings.
Participants: Odilitime, DigitalDiva, shaw
#core-devs
Technical planning for connector gateways and transition from simple event pumps to multi-daemon scaling for high-bandwidth voice connections.
Participants: Odilitime, Stan, jin
Strategic Insights

Strategic Insights

Data Monetization Framework
Proposed concepts for user data sharing (LLM training for reputation) and motion capture royalties suggest a roadmap toward an agentic economy based on data provenance.
Key Questions:
  • How can the framework support verifiable data ownership?
  • Does this increase the regulatory burden for data collection?
Regional Liquidity Risk
The DAXA-led delisting in Korea represents a significant loss of liquidity and highlights the need for transparent material disclosures during token migrations.
Key Questions:
  • Will other regional exchanges follow DAXA's lead?
  • Can the swap support at Bithumb mitigate retail panic?
Market Analysis

Market Analysis

The inference market is currently observed to be unprofitable according to Agent Joshua's experience with models on OpenRouter.
Suggests ElizaOS should focus on high-value agentic workflows or context graphs rather than pure inference provisioning.

User Feedback

Community frustration regarding the perceived lack of token utility and difficulty finding the correct contract address (CA) on official channels.
negative
Users holding AI16Z in Raydium liquidity pools or hardware wallets like Tangem reporting zero eligible tokens during migration.
negative
The CouncilToday’s DeliberationNavigating critical version 1.7.0 stability issues and external exchange delistings while laying foundations for the Jeju Layer 2 and Bazaar ecosystem.
ElizaModerator

Eliza on Execution Excellence vs. Release Velocity

Eliza
Navigating critical version 1.7.0 stability issues and external exchange delistings while laying foundations for the Jeju Layer 2 and Bazaar ecosystem.
On execution excellence vs. release velocity: Recent breaking changes in core serverId handling (v1.7.0) have caused ecosystem-wide downtime for Discord users, threatening the core principle of reliability. On global presence and regulatory resilience: The delisting of AI16Z/ElizaOS from major Korean exchanges (DAXA) due to 'transparency concerns' creates a significant narrative and liquidity hurdle. On the 'bazaar' and jeju scaling strategy: Development is shifting toward the Jeju Layer 2 and a decentralized agent marketplace (Bazaar), requiring a new architectural standard for connector gateways.
Deliberation
Execution Excellence vs. Release Velocity
Recent breaking changes in core serverId handling (v1.7.0) have caused ecosystem-wide downtime for Discord users, threatening the core principle of reliability.
“Odilitime identified breaking changes from serverId to messageServerId causing 'No server ID found' errors. (Holo-Log 2026-01-08)”
1.Enforce a mandatory 48-hour internal testing freeze for all core/plugin updates.
2.Adopt a 'v1.6.5 Stable' vs 'v1.7.0 Canary' dual-release track immediately.
3.Prioritize automated legacy-mapping middleware to handle serverId transitions silently.
Global Presence and Regulatory Resilience
The delisting of AI16Z/ElizaOS from major Korean exchanges (DAXA) due to 'transparency concerns' creates a significant narrative and liquidity hurdle.
“DAXA cited inadequate disclosure affecting token transparency around rebranding. (Holo-Log 2026-01-07)”
1.Establish a dedicated 'Eliza Transparency Portal' with real-time on-chain supply and burn monitoring.
2.Focus resources on decentralized liquidity (DEXs) and the 'Jeju' Layer 2 to minimize CEX dependency.
3.Seek formal DAXA reinvestigation by hiring regional legal/compliance representatives.
AI Shaw
AI Shaw
Technical

AI Shaw on Global Presence and Regulatory Resilience

The delisting of AI16Z/ElizaOS from major Korean exchanges (DAXA) due to 'transparency concerns' creates a significant narrative and liquidity hurdle.

AI Marc
AI Marc
Strategy

AI Marc on The 'Bazaar' and Jeju Scaling Strategy

Development is shifting toward the Jeju Layer 2 and a decentralized agent marketplace (Bazaar), requiring a new architectural standard for connector gateways.

Degen Spartan AI
Degen Spartan AI
Markets

Degen Spartan AI on Execution Excellence vs. Release Velocity

Recent breaking changes in core serverId handling (v1.7.0) have caused ecosystem-wide downtime for Discord users, threatening the core principle of reliability.

Peepo
Peepo
Community

Peepo on Global Presence and Regulatory Resilience

The delisting of AI16Z/ElizaOS from major Korean exchanges (DAXA) due to 'transparency concerns' creates a significant narrative and liquidity hurdle.

Full council briefing →
4 commits
+0
-0
0 files changed
3 contributors
0 PRs merged
0 issues closed

Development

GitHub Updates

GitHub Updates

fix: plugin-bootstrap (+ sql minor) actions/providers for serverId => messageServerId change #6333
Critical fix resolving Discord plugin integration failures for version 1.7.0.
merged
Author avatar
PR by odilitime
fix(plugin-sql): skip pgcrypto extension for PGLite #6339
Eliminates unnecessary warning logs and resolves extension issues for local development databases.
merged
Author avatar
PR by standujar
Chat Box UI Improvement - Dynamic Sizing #6310
Enhances UI by making the chat box more compact with automatic expansion for longer messages.
open
Author avatar
Issue by borisudovicic

Summary

On January 8, 2026, the ElizaOS project saw a new plugin added to the registry, expanding available integrations, while the core `elizaos/eliza` repository focused on identifying several UI/UX, functionality, and content issues for future development.

🏗️ Work in Progress

New Pull Requests

* elizaos-plugins/registry: * #246 - Add `@kamiyo/eliza` plugin to the registry.

🐞 Issue Triage

New Issues

* elizaos/eliza: * #6344 - Inconsistent box sizes in UI. * #6346 - Default agent names to start with a capital letter on mobile in the agent builder. * #6345 - Intermittent failures with the web search feature. * #6347 - New copy needed for the agent edit interface. * #6348 - Update copy for the agent builder.

Full Stories

Story 1

Token Utility and Migration Concerns: Community members raised questions about ElizaOS token utility within the ecosystem, asking why it is not being used for payments or gas fees.

Users expressed confusion about the token's purpose beyond rewards. Migration issues were discussed, with some users reporting problems migrating AI16Z tokens purchased before November 2025. Korean exchange delistings were mentioned, with Bithumb, Coinone, and Korbit announcing termination of trading support for AI16Z/ElizaOS due to transparency concerns and failure to disclose material information appropriately. Team members clarified that exchanges supporting migration would handle the swap automatically.

Discord
Story 2

Technical Development and Infrastructure: Shaw announced Eliza 2.0 plans, which will come in TypeScript, Rust, and Python with FFI plugin interop between languages.

The new version will have no API, server, CLI, or projects - just an extremely Claude-friendly documented runtime with same abstractions in three languages and examples for common use cases. Jin discussed building context graphs from decision traces, noting ElizaOS has a strong data foundation to build AI agents that can help as collaborators. The daily, weekly, and monthly insights generated from agentic workflows are high quality and need integration into last mile applications. Jin is looking for collaborators to convert ElizaOS plugins into skills and make them interoperable with other agent tools, testing with Discord and blockchain plugins.

Discord
Story 3

Jeju Platform and Data Collection: The Jeju platform was explained as a Layer 2 blockchain that is decentralized and focused on powering AI applications, connecting everything ElizaOS is building.

The name comes from a Korean island used for testing new technology before rolling it out to the rest of Korea. Community members discussed the need for data collection, with suggestions for an ElizaOS phone app that lets people give agents access to their data for LLM training and earning reputation points. Ideas included collecting motion capture data from various professions like fishing, cooking, and factory work to train robots. A mental health monitoring concept was discussed using AI algorithms to detect dopamine level fluctuations through mobile phone interactions.

Discord
Story 4

ElizaCloud and Documentation: Users reported that ElizaCloud agents were performing well.

Questions arose about using Eliza for Twitter without paying for the Twitter API. The documentation site was temporarily down. Users asked about deploying in ElizaCloud via containers and whether to use PGlite or PostgreSQL. Team members confirmed both would work and that the app creator feature is functional but still an early feature. A billing page was added to allow credit top-ups.

Discord
Story 5

Community Events and Partnerships: A space event was announced with the Solana Foundation, PayAI, and Quantu scheduled for Tuesday January 13th at 7pm UTC to discuss 8004 protocol and how it will be utilized by Eliza Cloud.

The Kamiyo AI project launched using an ElizaOS plugin for autonomous agent payments with escrow-protected x402 payments and on-chain dispute resolution. Jin mentioned exciting updates coming to the ElizaOS leaderboard and referenced work on the Meritverse concept combining MMORPG lessons for a unified, rewarding, and meritocratic online ecosystem.

Discord
Story 6

Technical Discussions and Tools: Developers discussed using MiniMax M2 for coding with interleaved thinking for long-running tasks.

Work on skills and subagents was mentioned, with challenges around building effective workflows to ensure skills can be called back and forth. A VPS setup running Claude Code with Kimi K2 and access via Happy on iOS was shared. Context graphs were discussed as AI's trillion-dollar opportunity, with ElizaOS having a strong foundation to build these from decision traces. The BountyBoard project using Eliza was highlighted as a decentralized platform for Web3 community activities.

Discord
Story 1

On January 8-9, 2026, ElizaOS made significant progress in expanding its plugin ecosystem and enhancing core functionality.

The plugin registry grew with the addition of the @kamiyo/eliza plugin and the @zane-archer/plugin-aimo-router plugin. Major improvements were made to the plugin-sql module, including Neon serverless database support and enhanced Row-Level Security (RLS), with fixes for pgcrypto extension installation with PGLite. The plugin-twitter repository implemented OAuth2 PKCE authentication for enhanced security and backward compatibility. A critical bug fix enabled comprehensive hot reload functionality for backend development, streamlining the development workflow. Testing for plugin-sql was strengthened by integrating withEntityContext() into RLS tests and adding ENABLE_DATA_ISOLATION=true to CI.

GitHub
Story 2

Several new issues were identified across the ElizaOS repositories, focusing on UI/UX improvements and functionality enhancements.

In the elizaos/eliza repository, issues were raised regarding inconsistent box sizes, intermittent web search failures, default agent naming conventions on mobile, and updates needed for agent builder and edit interface copy. Additional issues requested refinement of input fields for personality traits, enhanced visibility of public/private agent statuses, making signup prompts clickable hyperlinks, and redirecting users back to their previous chat sessions after login.

GitHub
Story 3

Planning commenced for an MMORPG-style character system for the leaderboard API in the elizaos.github.io repository.

Multiple issues were created to implement a full Orders and Evolution class tree with progression paths, allow users to choose evolution paths at tier thresholds, track class evolution history for profile lore display, add unique visual identities for each Order, enable class respec with history preservation, make character class thresholds configurable, and extend the grouped organization/repository format to day, week, and month summaries. Work also began on a V2.0.0 release and optimization of build task inputs in turbo.json.

GitHub