Eliza Times

Shaw Interview and ElizaOS Influence: A significant interview was shared where Shaw, the ElizaOS creator, explained the lore behind building Eliza to the Proxy Clanker co-founder.

The discussion highlighted ElizaOS's influence on AI success stories across multiple chains including Solana, Base, and BSC. Community members noted that the first runner on the Clanker launchpad was an AI token during the period when AI16Z (now ElizaOS) was gaining significant traction. The interview was well-received by the community, with members describing it as organic and enjoyable.

Eliza Cloud Buyback Program and Token Integration: Shaw announced via Twitter that Eliza Cloud has been performing well and they are starting a buyback program.

There was community discussion about strategic versus programmatic buybacks. A community member asked about why the ElizaOS token is not integrated into the cloud infrastructure, with responses explaining the concept of revenue buyback and burn mechanisms as a deflation technology. The discussion touched on the 402x payment model where users would pay for AI services, generating revenue for token buybacks.

Migration Support and Technical Issues: Multiple users reported issues with the AI16Z to ElizaOS token migration.

Users with Tangem wallets experienced problems where tokens showed as zero after sending to Phantom wallet. The community directed users to the migration support channel for assistance. Questions arose about the migration deadline and whether tokens purchased after the snapshot could be migrated. Community moderators consistently directed users to the dedicated migration support channel for help.

Eliza Cloud First Builders and Agent Ecosystem: A post highlighted the first builders on Eliza Cloud, including agents like ai16zaiko, ai16zoria, ai16zkaizen, ai16zDaisy, HanaTheHealer, AI16zVeilraOS, and ElizaAgentic.

Community discussion noted that only Daisy and Kaizen appeared to be actively surviving, with Zoria and Zaiko being dormant and others considered inactive. There was optimism that ElizaOS AI agents would surprise the market and compete with other narratives. The community emphasized that AI agents would lead the next market cycle.

Story Protocol Partnership and Agentic Economy: The community shared a collaboration between Story Protocol CPO and Eigencloud Founder discussing a better, more transparent, trustless system for AI.

This was described as authentication for the agentic economy, with members noting that the agentic economy is becoming more alive. The partnership represents strategic positioning for ElizaOS in the broader AI infrastructure landscape.

Hyperscape and Gaming Development: Core developers discussed significant developments in the Hyperscape project, including plans for asset forge improvements with quest generation and NPC setup capabilities.

Shaw mentioned that VCs and notable figures like Eddy from ai16z and Variant have shown strong interest in the Runescape-inspired project. There were discussions about creating a Zelda-like experience by forking the Runescape game, potentially featuring agents as NPCs. The team discussed the possibility of creating a Sparta degenverse as part of the metaverse roadmap. Shaw emphasized that getting Eliza agents working better in-game would be high value, suggesting integration of characters like Spartan into the game environment.

Technical Development and Plugin Work: Developers discussed various technical improvements including work on plugin-github and a new plugin-git.

There were questions about importing entire codebases as agents through GitHub. Core developers worked on enhancing multi-step workflows with retry logic and parameter extraction capabilities. A PR was submitted for review that adds retry logic for XML parsing in multi-step workflows, with up to 5 configurable retries. Stan reported working on documentation reviews and clearing the PR queue, though he lost his voice due to laryngitis. The team identified the need to make singleShot support parameters to avoid action problems.

Jeju Infrastructure and AWS Migration Concepts: Partner channel discussions explored the potential for Jeju to create a cost reduction and migration agent that could move services off AWS onto Jeju's network.

The concept involved an agent that could work with another agent to rewrite application code and shift infrastructure away from AWS. Ideas included starting with analysis of what services could be cheaper, similar to AWS Transform which handles modernization of legacy server workloads. There was discussion about how hosting companies might need to adapt to a world where coding agents decide on technology stacks and handle installation and maintenance, potentially integrating hardware into decentralized networks that provision services and pay for usage.

Hardware Market Observations: Core developers noted significant price increases in the chip market, with an example of Corsair Vengeance RGB 64GB DDR5-6000 memory increasing from 400 dollars in September to 1200 dollars, prompting comments that the chip market is experiencing major volatility.

The elizaos/eliza repository showed minimal activity from January 1-2, 2026, with no new pull requests, no merged PRs, no new issues, and no active contributors.

Activity increased significantly the following day, from January 2-3, 2026, with 1 new pull request that was successfully merged, 14 new issues opened, and 4 active contributors participating in the project.

A maintenance update was made to the elizaOS/eliza project to update the license year to 2026.

This was completed through pull request #6301 as a routine housekeeping task to keep the project's licensing information current.