ZetaChain's governance proposal to migrate its native ZETA token to Solana has received overwhelming support, with 99.4% of voters backing Proposal 68. According to reports from crypto.news, the voting period closed at 14:58:18 UTC on September 20 after a standard 72-hour period. The proposal achieved 58% participation with only 0.3% voting against and 0.3% abstaining, surpassing the required 40% quorum threshold. The migration would establish Solana as ZETA's canonical network while retaining the token's existing ticker and total supply through a 1:1 conversion. However, as reported by 99Bitcoins, the vote does not switch off ZetaChain overnight - core contributors must still submit a second proposal defining the shutdown timetable, and until that proposal passes, the existing Layer 1 blockchain keeps running.
The migration would convert ZETA from its current 18 decimal places to 9 decimal places on Solana, with balances rounding down to the nearest supported precision. As reported by crypto.news, existing vesting schedules would continue through their original dates, and no new tokens would be created during the conversion process. The project has ruled out maintaining the new Solana asset as a wrapped representation, stating that a bridge would depend on the original chain continuing to operate while the current plan eventually shuts that chain down. ZETA already issued on Ethereum and BNB Chain remains outside the scope of the current governance proposal, with the current proposal specifically covering ZETA native to ZetaChain only.
A successful Proposal 68 vote only approves the migration direction and authorizes core contributors to prepare a second proposal containing the actual migration mechanism, snapshot height, claim process, and exchange arrangements. According to crypto.news, Proposal 2 must establish the block height used for the balance snapshot, connected-chain withdrawal window, chain halt, Solana claim process, and exchange conversion period. As reported by 99Bitcoins, validators will keep operating, and staking rewards will continue through the transition. The project plans to publish the snapshot export and checksum so balances can be independently reproduced, with an archive node and explorer remaining accessible after shutdown. Staking rewards would continue until the shutdown time specified in Proposal 2, with future staking mechanisms remaining 'under active exploration'.
ZetaChain's private multi-model AI application Anuma and its Private Memory Layer would move to Solana as part of the project's new technical focus. As reported by crypto.news, more than 301,000 people have joined Anuma since February, with the application passing one million requests across 35 AI models. The application uses encrypted memory intended to remain under user control while closed model providers receive only context required for individual requests. ZETA already has utility inside Anuma, where users can lock tokens to receive credits for AI usage, with locked tokens removed from circulating supply while committed. According to 99Bitcoins, ZetaChain describes the Private Memory Layer as letting users carry encrypted context across different AI models, though this represents the project's company claim about the product's design rather than an independently verified security audit.
The migration addresses operational challenges associated with ZetaChain's Cosmos-based infrastructure. According to crypto.news, the proposal specifically cites maintenance burden inherited from Cosmos SDK and related components, referencing an August 25 security response where attackers exploited a critical Cosmos EVM vulnerability across six chains. The project cited Solana's 400 millisecond confirmations and sub-cent settlement capabilities as suitable for repeated AI-agent transactions. However, as reported by 99Bitcoins, ZetaChain itself was not named among the networks exploited in that incident. The project has its own security history to reckon with, having suffered a reported $334,000 exploit in April targeting its cross-chain gateway contract, and later acknowledged dismissing an earlier bug bounty report about the vulnerability as intended behavior - a lapse that prompted a review of its security processes.
