Eliza Times

Kraken Exchange Migration Announcement - Positive news emerged for Kraken users holding AI16Z tokens.

According to an email shared by community member Serikiki, Kraken will distribute ElizaOS tokens on December 19, 2025 at 3:00 PM UTC. The distribution follows a 1:6 ratio based on a snapshot taken on November 11, 2025 at 11:40 UTC. Only accounts holding AI16Z at the snapshot time are eligible. AI16Z trading remains disabled, but withdrawals will reopen on December 19. ElizaOS trading and funding will also begin at the same time. The community expressed gratitude to the team for resolving this situation with Kraken.

Bithumb Migration Tensions - Korean community members expressed frustration about delays in the Bithumb exchange migration process.

Users complained about lack of communication regarding progress and demanded updates from foundation officials. Community helpers explained that the migration responsibility lies with the exchange, not the foundation, and that the migration was announced months in advance. Some users argued that busy people may have missed announcements despite the advance notice. The team recommended users contact Bithumb support directly about the delays.

Development Progress Updates - Odilitime provided updates on Spartan development, stating the team has been working on getting it ready for cloud deployment, Babylon integration, and wider Discord distribution.

Core developer Stan demonstrated cloud streaming functionality with a video showing the feature working in the monorepo, though noting that Actions UI still displays text all at once instead of streaming. The team is working on fixing the rendering issue. Stan also mentioned plans to work on authentication PR rebasing and additional testing.

Vibe Coding Philosophy and Best Practices - Core developer cjft introduced a new rule requiring PRs larger than 20 lines to include a video demonstration of the feature working.

The team discussed efficient coding practices using AI tools like Cursor, with cjft explaining that much of development can be streamlined by copying tasks into AI tools, reviewing outputs, and fixing errors by pasting terminal logs. The discussion emphasized that real thought is needed for architectural decisions and design tweaks, but routine tasks can be automated. Developers shared tools like claudekit for Claude Code and discussed using git worktrees for managing multiple development streams simultaneously.

Technical Support and Database Issues - Multiple developers reported issues with PostgreSQL database migrations.

User fenrirfawks encountered migration errors despite creating a local PostgreSQL database. Stan provided troubleshooting assistance, asking about database version, user permissions, and connection validity. The issue appeared related to database accessibility and user permissions for creating in the public schema. Another user reported Twitter replies causing database failures due to foreign key constraints, with suggestions to try the latest codebase which includes SQL fixes.

Community Engagement and Resources - User thirti.eth reported successfully getting an agent running with Polymarket bets being tracked to a Neon database table and deployed to GitHub and Fly.io, though still working on getting the agent to understand conversation topics.

The team shared resources including an open source coding agent project and discussed hosting recommendations, with Odilitime suggesting Hetzner or OVH as preferred VPS providers. A reminder was posted about an ongoing contest in the creative channel offering 100,000 ElizaOS tokens for art, video, app, or other creative submissions.

Partner Channel Discussion - In the partners channel, untitledxyz suggested rebranding the channel as an Eliza-Alpha channel to preview cloud and other developments, inviting strategic people to get glimpses of demos and teasers that could be tested and shared.

Shaw responded positively to the suggestion, indicating openness to this approach for the post-migration era.

Legal and Industry News - The core developers channel shared an update about a lawsuit involving Pumpdotfun and Solana, where leave to amend and file a new complaint was granted.

The complaint alleges that what appeared to be a fair, automated marketplace was structurally tilted to extract value from ordinary users while rewarding those with privileged access to Solana.

Issue #6246 by borisudovicic addresses the implementation of web search functionality within the eliza project.

Issue #6245 by 0xbbjoker proposes adding the ability to pre-upload files in the agent creator for RAG (Retrieval-Augmented Generation) purposes.

Over December 15-16, 2025, ElizaOS made significant progress in expanding its plugin ecosystem and improving user experience.

The project focused on architectural advancements, bug fixes, and extensive UI/UX enhancements across the platform.

Plugin Ecosystem Development: The plugin ecosystem saw major advancements with refactoring efforts in plugin-discord for message handling and plugin-telegram for implementing a unified messaging API with enhanced ElizaOS integration.

A new self-hosted Farcaster plugin (plugin-farcaster-local-hub) was introduced to the registry, enabling local Snapchain/Hubble hub integration without external API dependencies and including fixes for Farcaster timestamp epoch and Hub API parameters.

Core System Improvements: The core eliza repository focused on critical bug fixes and optimizations.

Key accomplishments included fixing an API signature mismatch in CLI e2e-tests, correcting unit test mock function names for character retrieval, and implementing smooth migration from pre-1.6.5 to 1.6.5+ schema conventions within the SQL plugin. The SQL plugin optimization also included improved Row-Level Security (RLS) handling and comprehensive test coverage.

UI/UX Enhancement Initiative: A comprehensive set of UI/UX improvements were proposed and implemented, focusing on agent and app management.

Key enhancements included redesigning the dashboard to prioritize agent and app creation with monetization opportunities, implementing guided onboarding overlays for new users, and adding a chat interface to the landing page for goal-oriented user routing. The Apps section was elevated to a first-class product section.

Agent Creation and Management Improvements: Multiple enhancements were made to streamline agent creation and management workflows.

These included adding post-agent-creation next steps for deployment guidance, implementing tooltips for Style and Personality tabs, adding placeholder text to empty input fields, and allowing text input while an agent is processing. Button labels were renamed for clarity, with Save changed to Deploy and Build changed to Edit for existing agents. A three-dot menu was added to agent cards for quick edit and delete options.

Plugin and File Management Enhancements: Visual feedback for plugin selection was improved with a transition to more prominent full background color changes and refined toggle selection mechanisms.

The file upload process was streamlined by increasing visibility of the Choose Files button and removing the two-step upload process. The Knowledge section was renamed to Files, and technical terminology like RAG was replaced with plain language. Similarly, MCP was replaced with Services in the UI for better user understanding.

Bug Fixes and New Feature Discussions: Several bugs were addressed, including avatar mismatch between edit view and sidebar, and edit mode chat suggestions incorrectly triggering agent responses.

New feature discussions began around implementing web search capabilities and pre-uploading files for RAG knowledge during agent creation to improve the user experience. A proposal was also made for an AI Agent Payment Implementation Guide using Circle and Coinbase APIs.

During the period from December 16 to December 17, 2025, the elizaos/eliza repository showed minimal activity with no new pull requests created or merged.

However, the project saw 2 new issues opened and maintained engagement from 4 active contributors during this timeframe.