Akash Opens Vote to Migrate Network to Solana

Akash Network has opened governance voting on a plan to leave its sovereign Cosmos-based blockchain and rebuild its decentralized cloud marketplace on Solana. According to the official Akash migration report, Proposal 346 asks AKT stakers to approve Solana as the network’s future execution layer while separating the token migration from the later marketplace cutover. Voting remains open through November 2.

Early participation strongly favors the proposal. An October 26 on-chain snapshot showed approximately 37.7 million AKT voting yes against about 656,000 no, representing roughly 98% support and turnout above the 33.4% quorum requirement. Those figures establish strong preliminary support but do not constitute a final governance result while the voting window remains open.

AKT Would Move Before the Compute Marketplace

If Proposal 346 passes, AKT would become a Solana token through a one-way migration process. Holders would receive SPL AKT at a 1:1 ratio while preserving the existing ticker, six-decimal format and total token supply, with Cosmos-side AKT removed from circulation as corresponding Solana tokens are issued. The migration portal is planned to remain available for two years.

The token launch is conditional on two independent security audits covering the token and migration portal. Akash’s public report targets launch roughly two weeks after governance approval, while the submitted proposal describes an expected two-to-three-week window after passage and successful audits. The timetable is therefore conditional rather than a fixed token-launch date.

The compute marketplace itself would remain on akashnet-2 until a separate cutover proposal is approved. No marketplace migration date has been established, and Akash plans additional audits, a provider testnet and migration rehearsals before governance can authorize the point at which new deployments begin moving to Solana.

Solana Offers Shared Infrastructure for DePIN

Akash says maintaining its own validator set and customized Cosmos stack creates operational overhead that its marketplace no longer requires. Moving to Solana would replace Akash’s independent consensus system with shared Solana security while reducing the core team’s responsibility for maintaining Cosmos SDK, CometBFT and chain-specific upgrade infrastructure.

The choice also places Akash alongside decentralized infrastructure projects already operating around Solana. Networks such as io.net are using Solana for coordination and payments while expanding distributed GPU services for autonomous applications, and Render is developing higher-level AI routing infrastructure. Blockchain settlement remains separate from the physical GPU workloads these networks provide, including the compute marketplace Akash intends to preserve after migration.

Solana’s own infrastructure recently changed through the Alpenglow consensus upgrade, which replaced TowerBFT with Votor and substantially shortened finality targets. Akash’s decision relies partly on Solana’s existing throughput, liquidity and DePIN ecosystem, but those advantages do not eliminate migration risk.

If the later marketplace cutover eventually occurs, existing Cosmos workloads would continue running for 90 days while users redeploy. Staking rewards on the old chain would end at cutover, while validators would continue supporting the wind-down until the final halt. Until Proposal 346 finishes voting and subsequent governance stages are completed, Akash remains operational on its existing Cosmos chain.