Eliza Times

Kraken Exchange announced the finalization of ELIZAOS token distribution plans following the AI16Z token migration.

The snapshot was taken on November 11, 2025 at 11:40 UTC. Users who held AI16Z at that time will receive ELIZAOS at a 1:6 ratio, regardless of their current AI16Z balance. Token distribution is scheduled for Friday, December 19 at 3:00 PM UTC. AI16Z trading remains disabled, but withdrawals will reopen on December 19. ELIZAOS trading and funding will also open at the same time. Only accounts holding AI16Z at the time of the snapshot are eligible. The community expressed gratitude to the team for managing this situation with Kraken.

The Korean community expressed significant frustration regarding the Bithumb exchange situation.

Bithumb maintained that it was informed of the snapshot at a late stage and kept deposits open and allowed trading even after the November 11 snapshot. Bithumb initially announced that all balances would be swapped, but later reversed their position, claiming the team took the snapshot without prior notice. Korean holders requested evidence of when the team notified Bithumb and details about the negotiation process. The team responded that they are not commenting on the Bithumb situation until their response becomes clearer, and noted that aggressive communication does not result in better outcomes. The team emphasized they have not abandoned any part of their community but that ongoing outbursts from Korean community members are wearing thin.

Core development team members discussed vibe coding practices and workflow optimization.

A new rule was proposed requiring PRs larger than 20 lines to include a video demonstration of the feature working. Developers shared techniques for efficient coding using AI tools like Cursor, including running multiple prompts simultaneously, using environment containers, and leveraging git worktrees. The team emphasized that much of the coding work can be automated through AI assistance, with real thought required mainly for initial architecture decisions, design tweaks, and performance optimizations. A mandatory class on how to vibe code is planned for all developers.

Stan demonstrated progress on cloud streaming functionality for the ElizaOS platform.

Everything works in the monorepo, but for Actions the UI still displays text all at once instead of streaming it, though the stream itself is fine. The issue is just with rendering on actions. Stan plans to switch to the 402x PR and rebase the authentication PR on the monorepo. The cloud PR was pushed for additional testing. Streaming now works for simple messages and actions.

Odilitime provided updates on Spartan development, stating he has been working on getting Spartan ready for cloud deployment, Babylon integration, and wider Discord distribution.

He also shared insights about Cursor AI's web search capability, noting that it can search the internet but requires prompting with phrases like look for any prior work on the Internet to help bring in ideas.

A developer successfully got their agent up and running with Polymarket bets being tracked to a table in Neon database and deployed to GitHub and Fly.io.

They are now working on getting the agent to understand what it is supposed to talk about. Another developer encountered PostgreSQL migration issues when trying to set up ElizaOS with a local database. After troubleshooting with Stan, they worked through permission issues and database configuration problems. The developer was advised to check user permissions for creating in the public schema.

Developers discussed extending agent actions by creating custom action files in the actions folder.

Odilitime recommended cloning plugins into the packages folder. Stan directed developers to the ElizaOS documentation on components including Actions, Providers, Evaluators, and Services. Developers were reminded that custom actions also need to be registered in the src/index file.

The core development team shared technical resources including Claude Skills documentation, a research paper on scaling agent systems, and a GitHub PR quiz concept.

Odilitime announced an upcoming merge of a significant Discord plugin PR that implements resumable channel history fetching, LLM-assisted message splitting, richer permission and audit events, a startup banner, and improved media and summarization handling with new tests. The PR had grown to 66 commits over three weeks. Stan requested time to review before merging. The team also shared a comprehensive API mega-list repository for building applications.

Community members discussed the token price decline and market conditions.

Some expressed concern about the price dropping to lower levels, while others remained optimistic about the project's future. There was discussion about someone purchasing 10 percent of Shaw coin, with speculation about potential upcoming developments. A reminder was posted about an ongoing contest in the creative channel offering 100,000 ELIZAOS tokens for art, video, app submissions, or other creative content. The migration site was confirmed to be safe for use.

In the partners channel, there was discussion about market makers and the need for agents to be in production and consistently engaging in social spheres before market maker involvement.

It was noted that the Pippin developer is a VC who became curious about how LLMs work. The emphasis was placed on getting to the point of having something live that is incrementally improving.

Several bug fixes have been addressed by borisudovicic.

Issue #6243 resolves a problem where chat suggestions in edit mode were incorrectly triggering agent responses. Issue #6242 fixes an avatar mismatch issue between the edit view and sidebar, ensuring consistent visual representation across different interface sections.

Issue #6240 proposes replacing technical RAG terminology with plain language to improve user understanding and accessibility.

This change aims to make the interface more user-friendly for non-technical users.

Issue #6246 introduces web search functionality, submitted by borisudovicic, expanding the capabilities of the platform.

Issue #6245 by 0xbbjoker proposes adding the ability to pre-upload files in the agent creator for RAG purposes, enhancing the agent creation workflow.

Over a two-day period from December 16-18, 2025, the elizaos/eliza repository showed minimal pull request activity with no new PRs created or merged on either day.

However, issue activity increased significantly from 2 new issues on December 16-17 to 14 new issues on December 17-18, representing a seven-fold increase. Active contributor participation remained relatively stable, with 4 contributors active on the first day and 3 on the second day.