Bitcoin
Akash prepares its move to Solana following the November 2 vote
The community approved the decentralized computing network’s migration in principle. Launching AKT on Solana and moving the marketplace are separate steps subject to checks.

The vote approves a direction, not a completed transfer
Akash confirmed on November 2 that it had chosen Solana to host its decentralized computing infrastructure, following approval of governance proposal 346. The announcement reports support of about 97% of votes. The decision concerns a service connecting independent computing providers with users, including for artificial intelligence. It commits to a transition from Akash’s own Cosmos blockchain, but does not mean all services are already operating on the new infrastructure.
The November 2 release envisages migration over the following twenty-four months. It names Akash Marketplace, the AkashML inference platform and Homenode among the businesses expected to become native to Solana. This broad timetable does not replace the project’s detailed technical conditions. The team’s October 26 report separates the token launch from the marketplace cutover, which still requires audits, rehearsals and a separate governance decision setting a date.
The AKT token is set to precede the marketplace
Holders are expected to be able to convert AKT into an SPL version on Solana at one token for one token. The report describes a one-way portal open for two years from token launch. A completed conversion must therefore not be presented as a round trip between networks. The team makes launch conditional on two independent audits. Indicative timing announced around the vote does not itself prove that the portal has actually opened or invite users to use an address found elsewhere.
Existing workloads are meant to continue before the marketplace cutover. The plan then provides a ninety-day transition for existing leases on the old chain before it halts. Exchanges are expected to organize customer migrations on their own schedules. Holding a token, renting compute and operating infrastructure are therefore different situations. Moving the token to another network does not automatically transfer every application or computing contract.
Expected savings come with transition risks
Akash bases its choice on less work maintaining its own blockchain, transaction costs and Solana’s decentralized computing and physical infrastructure ecosystem. These are the team’s arguments and estimates, rather than savings already measured after migration. The project also means giving up its own consensus and some native Cosmos connections. The old chain’s validator activity and revenue are scheduled to end at separate stages, under the published plan.
The report identifies risks involving the portal, matching supplies across chains, fake migration websites and changes to operators’ tools. Audits and controls seek to reduce these risks without guaranteeing the transition’s outcome. The completed decision is the November 2 approval; the next useful evidence will be audit reports, official instructions and the vote setting cutover. Neither community approval nor the conversion ratio guarantees AKT’s value.
