Eliza Times

Token Utility and Exchange Listings Discussion: Community members raised questions about ElizaOS token utility within the ecosystem, noting that current documentation does not clearly explain how the token is used beyond rewards.

There was discussion about Korean exchange delistings, with announcements from Bithumb, Coinone, and Korbit regarding termination of trading support for ai16z/ElizaOS. Korean community members explained that DAXA member exchanges determined the project had transparency issues during the migration process, making future listings in Korea unlikely. The team acknowledged they need to better communicate the contract address and token utility across official channels.

Migration Support and Issues: Users reported problems with token migration, particularly those holding tokens in liquidity pools or specific wallets like Tangem.

The migration support channel was directed for users experiencing issues with the snapshot-based migration from ai16z to ElizaOS. Some users reported seeing zero eligible tokens despite holding tokens before the November snapshot date. The team confirmed that exchanges supporting the migration would handle the 1:6 swap ratio automatically for eligible holders.

Jeju Layer 2 and Infrastructure Development: Developers discussed Jeju as a decentralized Layer 2 focused on powering AI applications and connecting ElizaOS ecosystem components.

The Bazaar was described as a decentralized marketplace application running on Jeju, functioning as an app store for agents. Shaw shared the Jeju cloud branch containing his preferred implementation of the Discord bridge. Discussion included plans for hybrid architecture with persistent workers and exploration of gateway patterns for different connectors.

Data Collection and Context Graphs: Jin shared an article about context graphs as AI's trillion-dollar opportunity, noting that ElizaOS has a strong data foundation to build context graphs from decision traces.

The team discussed how daily, weekly, and monthly insights generated from agentic workflows are high quality and need integration into last-mile applications. Community members proposed ideas for data collection through mobile apps that would allow users to share data for LLM training in exchange for reputation points. Discussion included potential applications for motion capture data collection for training robots in various professions.

Community Projects and Integrations: A new project called Kamiyo launched using ElizaOS plugins for autonomous agent payments, featuring escrow-protected payments with on-chain dispute resolution.

The BountyBoard project was shared as a decentralized platform for Web3 community activities that uses Eliza. Developers discussed integration challenges with Twitter API costs and whether ElizaOS provides alternatives to the 200 dollar monthly API fee.

Infrastructure and Deployment: Developers discussed deployment options for ElizaCloud via containers, with questions about whether to use Pglite or PostgreSQL.

The team confirmed either database option would work for container deployments. Discussion included cursor AI tool usage and notes that using personal Claude API keys does not provide the cursor-optimized version of Claude.

On January 7-8, 2026, ElizaOS made significant progress across multiple areas including plugin stability, UI/UX improvements, and ecosystem expansion.

The development team addressed critical bugs, enhanced security features, and expanded the plugin registry while identifying new areas for optimization and improvement.

CRITICAL ATTENTION NEEDED: The plugin-discord publishing failure remains unresolved.

Versions 1.3.4 and 1.3.6 failed to publish due to TypeScript compatibility issues with elizaos/config and elizaos dependencies. This deployment blocker requires immediate investigation and resolution.

PLUGIN STABILITY AND COMPATIBILITY: Major fixes were implemented for plugin-bootstrap and plugin-sql to address the serverId to messageServerId change, resolving issues for version 1.7.0 users.

The plugin-sql module was enhanced with Neon serverless support and improved Row-Level Security (RLS) for better security and scalability. Additionally, the pgcrypto extension was skipped for PGLite to resolve database extension issues.

UI/UX AND AGENT MANAGEMENT IMPROVEMENTS: Extensive improvements were made to the user interface and agent management systems.

These include: ensuring unique usernames for agents, handling blank agent name fields, removing agent avatars in chat menus, ensuring agent responses start from the top, implementing dynamic chat box sizing, improving chat summaries, fixing scrolling issues, enhancing agent sorting functionality, resolving refresh requirements after deleting conversations, implementing message limits for non-signed-up users, separating public agent states, adjusting free credit amounts, streamlining wallet connection processes, and implementing JWT authentication and user management.

PLUGIN ECOSYSTEM EXPANSION: The ElizaOS plugin ecosystem grew with the addition of the @kamiyo/eliza plugin to the registry.

Discord plugin improvements included confirmation that slash command functionality is now extensible, allowing developers to add commands as needed.

NEW ISSUES IDENTIFIED: Several new issues were reported requiring attention: inconsistent box sizes in the UI, intermittent web search functionality failures, default agent names needing to start with capital letters on mobile in the agent builder, new copy needed for the agent edit interface, and updates required for agent builder copy.

Additionally, optimization opportunities were identified for runtime initialization, database query patterns using UPSERT, provider batching for composeState, message processing parallelization, and a critical TOCTOU race condition in credit deduction for streaming endpoints. A feature request for Apps promotion was also proposed.

WORK IN PROGRESS: Active pull requests include addressing the use of handleMessage instead of sendMessage for the ElizaOS unified API in plugin-discord, and optimization work for runtime initialization focusing on parallelization and atomic upserts in the core eliza repository.

Between January 7, 2026 and January 8, 2026, the elizaos/eliza repository showed moderate development activity.

During this two-day period, there were 2 new pull requests submitted with 1 successfully merged. The repository also saw 7 new issues opened and had 7 active contributors working on the project.

A bug fix was implemented in the plugin-bootstrap and SQL minor components to update actions and providers.

The change addresses a renaming from serverId to messageServerId throughout the affected code. This fix was submitted as Pull Request #6333 in the elizaOS/eliza repository.