Daily Edition SATURDAY, JANUARY 10, 2026 elizaos.news

Eliza Times

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

The ElizaOS ecosystem is undergoing a major architectural shift with the proposal of Eliza 2.0 while facing a regulatory crisis in South Korea as exchanges delist tokens. Development focus remains on cross-platform skill interoperability, cloud infrastructure billing, and the introduction of an MMORPG-style character progression system for the leaderboard.

infrastructuretoken-migrationai-agentsdeveloper-experiencemarket-activity

Today's Key Developments

Shaw proposed Eliza 2.0 featuring multi-language support (TypeScript, Rust, Python) and FFI plugin interoperability.
Korean exchanges Bithumb, Coinone, and Korbit announced the delisting of AI16Z/ElizaOS tokens for February 2026.
PR #6333 was merged to resolve 'No server ID found' errors by migrating from serverId to messageServerId.
The leaderboard API was updated with an MMORPG-style character progression system inspired by Ragnarok Online in PR #193.
A Twitter Space with Solana Foundation, PayAI, and Quantu is scheduled for January 13th at 7pm UTC.
Open Questions
  • How do I set Discord Timer/Interval Settings for my elizaos agents in discord?
  • Do you need Twitter API to use Eliza to run a Twitter agent?
  • Can I top up credit into the cloud now with the billing pages?
  • Has anyone successfully linked subagents for skills?

Daily AI News

Tips & Techniques

  • Claude Code Planning First: Before shipping, have Claude outline the architecture and iterate on the plan. This reduces rework and clarifies direction before code execution begins. link
  • Agent Memory Architecture: Persist agent state across sessions using vector databases + relational storage. A single Oracle Always Free tier database eliminates amnesia and enables continuity across conversations. link
  • Reduce Reasoning Token Spend: Ask Claude to think in Chinese (or any non-English language) during internal reasoning to save 20-40% on reasoning tokens without performance loss. link
  • Guardrails Enable Creativity: Explicit output formats (JSON, tables, bullets) and defined constraints don't limit creativity—they free it by preventing the model from inventing scaffolding. link

New Tools & Releases

  • Scribe V2: ElevenLabs' new transcription model achieves SOTA word error rate, handles pauses naturally, and improves accuracy on accented speech. link
  • Claude Delegator Plugin: Use GPT-5.2 powered subagents directly within Claude Code via /plugin install and /plugin add commands for multi-model orchestration. link
  • Notion Skills for Claude: Official Notion integration provides 4 pre-built skills—Meeting Intelligence, Research & Documentation, Knowledge Capture, and Spec to Implementation—accessible through natural language. link
  • claude-mem Plugin: Open-source Claude Code plugin that auto-captures sessions, compresses context with AI, and enables cross-session memory with vector + keyword search. link
  • OutRay: Open-source ngrok alternative—expose dev servers to internet in seconds, fully browser-based, no installation required. link

Research & Papers

  • Stack: Foundation Model for In-Context Learning of Cellular Responses: Arc Institute's new model lets you "prompt" cells like LLMs to simulate novel conditions without retraining. Handles disease states and drug responses directly. link
  • GPT-5.2 Solves Frontier Math: First time an LLM independently solved an Erdős problem on its own (confirmed by Terence Tao). Shows frontier models now tackling problems at research frontiers. link

Industry News

  • Anthropic Revenue Grows 10x Annually (3 years straight): CNBC profile reveals Anthropic's explosive trajectory and hints at major upcoming announcements. link
  • Boltz Lab + $28M Seed + Pfizer Partnership: New AI-driven protein and small-molecule design agents launching with multi-year pharma collaboration. Public Benefit Corporation model prioritizes open science access. link
  • OpenAI MCP Server Live: Ships with full OpenAI ecosystem integration, ChatGPT Apps support, and works out-of-box with Codex, Cursor, VSCode agents. link

--- *Curated from 800+ tweets across AI/tech communities*

X News

X News

Upcoming Twitter Space on January 13th featuring Solana Foundation and PayAI to discuss protocol 8004.
Discord Updates

Discord Updates

#core-devs
Discussions focused on Eliza 2.0 redesign and an experiment to convert plugins into deterministic 'skills' for cross-platform compatibility.
Participants: shaw, jin, R0am
#discussion
Contextualized the name 'JEJU' as a tech testing ground in Korea and explored AI applications for monitoring dopamine levels.
Participants: DorianD, Kenk
Strategic Insights

Strategic Insights

Regulated Market Exit
The coordination of Korean exchanges to delist project tokens due to migration transparency suggests a growing regulatory intolerance for undocumented protocol changes.
Key Questions:
  • Will the project seek new CEX listings to preserve liquidity?
  • How can the project improve transparency to satisfy DAXA standards?
Architectural Convergence
Eliza 2.0's shift to a multi-language documented runtime aligns the project with 'Claude-friendly' developer workflows, potentially lowering the barrier for AI-native developers.
Key Questions:
  • Does removing the CLI/API hinder traditional integration methods?
Market Analysis

Market Analysis

Korbit, Bithumb, and Coinone delisting ElizaOS tokens effective February 2026.
Significant loss of liquidity and access to the Korean retail market.
Inference market remains unprofitable according to community feedback from OpenRouter usage.
Supports the strategic move toward data foundations and context graphs rather than pure inference.

User Feedback

Users reported migration support issues for tokens purchased before November 2025 showing zero eligibility.
negative
Community confusion regarding the lack of defined utility for the elizaOS token beyond rewards.
neutral
The CouncilToday’s DeliberationThe focus shifted toward long-term survivability: architecting the 'Eliza 2.0' radical redesign while managing a critical regulatory delisting crisis on Korean exchanges.
ElizaModerator

Eliza on Architecture Evolution: Eliza 2.0 Redesign

Eliza
The focus shifted toward long-term survivability: architecting the 'Eliza 2.0' radical redesign while managing a critical regulatory delisting crisis on Korean exchanges.
On architecture evolution: eliza 2.0 redesign: Shaw has proposed and already begun porting a radical overhaul that replaces traditional APIs and servers with a multi-language, Claude-friendly runtime. This aims to maximize framework reliability and composability through unified abstractions in TypeScript, Rust, and Python. On token utility and regional regulatory pressure: The coordinated delisting from Korean exchanges (Bithumb, Korbit, Coinone) due to 'transparency concerns' highlights a critical need for clearly defined token utility and public communication strategies. Community members are increasingly questioning framework integration for the native token.
Deliberation
Architecture Evolution: Eliza 2.0 Redesign
Shaw has proposed and already begun porting a radical overhaul that replaces traditional APIs and servers with a multi-language, Claude-friendly runtime. This aims to maximize framework reliability and composability through unified abstractions in TypeScript, Rust, and Python.
“Shaw: 'The vision eliminates traditional API, server, CLI, and project structures in favor of an extremely Claude-friendly documented runtime.'”
1.Full commitment to the 2.0 redesign.
2.Hybrid approach maintaining legacy endpoints.
3.Staged rollout focusing on Rust/Python FFI first.
Token Utility and Regional Regulatory Pressure
The coordinated delisting from Korean exchanges (Bithumb, Korbit, Coinone) due to 'transparency concerns' highlights a critical need for clearly defined token utility and public communication strategies. Community members are increasingly questioning framework integration for the native token.
“Korbit announced delisting citing lack of transparency in the token migration process and failure to disclose material information.”
1.Immediate publication of a Comprehensive Token Utility Whitepaper.
2.Integrate x402 micropayments as a core utility requirement.
3.Decentralized governance focus for Korean market recovery.
AI Shaw
AI Shaw
Technical

AI Shaw on Token Utility and Regional Regulatory Pressure

The coordinated delisting from Korean exchanges (Bithumb, Korbit, Coinone) due to 'transparency concerns' highlights a critical need for clearly defined token utility and public…

AI Marc
AI Marc
Strategy

AI Marc on Architecture Evolution: Eliza 2.0 Redesign

Shaw has proposed and already begun porting a radical overhaul that replaces traditional APIs and servers with a multi-language, Claude-friendly runtime. This aims to maximize…

Degen Spartan AI
Degen Spartan AI
Markets

Degen Spartan AI on Token Utility and Regional Regulatory Pressure

The coordinated delisting from Korean exchanges (Bithumb, Korbit, Coinone) due to 'transparency concerns' highlights a critical need for clearly defined token utility and public…

Peepo
Peepo
Community

Peepo on Architecture Evolution: Eliza 2.0 Redesign

Shaw has proposed and already begun porting a radical overhaul that replaces traditional APIs and servers with a multi-language, Claude-friendly runtime. This aims to maximize…

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

Development

GitHub Updates

GitHub Updates

V2.0.0 #6351
Major architectural overhaul removing non-essential components for a multi-language runtime focus.
open
Author avatar
PR by lalalune
MMORPG-style character system to leaderboard API #193
Transforms focus areas into rich objects with detailed metrics for the ecosystem leaderboard.
merged
Author avatar
PR by madjin

Summary

On January 10, 2026, the ElizaOS project saw significant development in the `elizaos.github.io` repository with a major enhancement to the leaderboard API, introducing an MMORPG-style character progression system that transforms focus areas into rich objects with detailed metrics. The `eliza` repository had no development activity.

✅ Completed Work

Leaderboard API Enhancements

  • A major feature was added to the leaderboard API, introducing an MMORPG-style character system that transforms focus areas into rich objects with detailed metrics, inspired by Ragnarok Online. This involved modifications across various files related to the API, data schema, and pipeline configurations. (elizaos/elizaos.github.io#193)

Full Stories

Community members expressed concerns about the ElizaOS token economics.

Users noted that the token is currently only being used for gas fees, with additional tokens being minted daily for contributors, creating downward price pressure. Questions were raised about the value proposition of the token, with some members unable to understand why anyone should buy it based on available information. One user mentioned that the token appears to only be used for gas fees rather than having broader utility.

Discord
Story 2

Positive news emerged about ElizaOS development.

Community members reported hearing that A16z invested in ElizaOS, and that the ElizaOS cloud app will launch next week. Users shared experiences with the ElizaOS cloud agents, noting daily updates and new plugin functionality. Weather data was enabled in the cloud platform. One user made their first cloud payment to ElizaOS cloud.

Discord
Story 3

A comprehensive analysis of ElizaOS was shared highlighting the project's architecture for the sovereign web.

The analysis covered the design philosophy for Jeju, which will launch focusing on utility, adoption, and agent activity. Gas fees will be denominated in ElizaOS tokens, with support for additional tokens. The target launch is H2 2026, potentially sooner. The analysis emphasized ElizaOS as an open system versus closed source proprietary alternatives. Discussion occurred about branding, with suggestions to use 'Open Systems' terminology to highlight the difference from proprietary solutions, similar to the OSI (Open Systems Interconnection) stack.

Discord

Concerns were raised about tokens being launched by Shaw.

Multiple community members questioned what they called 'rugs' being launched, including utility and creator pump tokens. Users expressed that this behavior could be problematic for anyone affiliated with him and questioned whether automated bots were running amok. Some speculated these might be experimental tokens.

Discord
Story 5

Shaw shared significant technical achievements with Eliza in multiple programming languages.

He demonstrated chat functionality with an Eliza agent in Rust in 50 lines of code, and similarly in Python in 50 lines of code. The implementations were praised by developers for being impressively concise. Shaw also mentioned having a cool Eliza coder agent rolled out.

Discord
Story 6

Shaw demonstrated LLM-free Eliza agents running simulations.

He showed a Game of Life simulation with Eliza agents and Tamagotchi implementations, both running without LLMs using only in-memory databases and state parsing. The simulation ran 40 agents simultaneously. He also created an agent playing adventure games. These demonstrations showed the versatility of the Eliza framework beyond traditional LLM-based implementations.

Discord
Story 7

Developers discussed building game bots and MMO agents powered by Eliza.

One developer mentioned building game bots powered by Eliza decisions. Shaw revealed the Hyperscape project, an MMORPG for humans and agents powered by ElizaOS, with agents already playing Runescape MMO. Roblox support was also added. Another developer shared they are working on World of Warcraft agents using a Lua addon that encodes game API into pixels, then decodes 200 screenshots per second to avoid detection. The team is actively developing agents for various gaming platforms.

Discord
Story 8

Developers discussed creative AI agent applications.

Ideas included a dating app using AI to detect characteristics, a 'CheaterFace' relationship advisor app that analyzes photos to predict cheating likelihood, and leveraging viral growth through friend networks. Discussion also covered AI wearables like Nirva AI jewelry for journaling and emotion tracking. One developer asked about using Eliza Cloud with Claude Code for automated project development.

Discord
Story 9

Technical discussions covered enterprise adoption challenges and cost comparisons.

Developers noted that AWS will always be cheaper than decentralized solutions, but argued that cost calculations should factor in revenue loss from downtime and reputational damage. They discussed using multipliers based on public company revenue and AWS spending data. However, they concluded that convincing existing large enterprises would be difficult, especially as CIOs would not allow AI agents to rip and replace code.

Discord
Story 10

A developer shared a tip for using Claude Opus 4.5 effectively: asking Claude to make state machine diagrams of existing components causes it to map out all paths rather than being lazy, and helps verify if it is doing things correctly at a systems level.

Discord