Akash Chooses Solana as New Home, Proposes 1:1 AKT Migration
Key Facts
Akash’s core team has chosen Solana as the project’s new home and proposed a plan that begins by moving the AKT token from the sovereign Cosmos chain akashnet-2 to a native format on Solana. The initial proposal does not automatically move the decentralized computing marketplace; converting the market requires a separate governance vote after audits and migration tests are completed. “The Akash core team has chosen Solana as the new home for the Akash Network,” the team said in its post. The first decision gate requires a 33.4% quorum and a majority in favor; if the proposal fails to meet that threshold, the plan returns to the options analysis stage. That puts the token migration decision at the start of a longer process, with later stages dependent on votes and testing.
Under the plan, AKT would launch on Solana as an SPL token two weeks after the migration proposal is approved, subject to passing two independent audits. At launch, a one-way token transfer portal would open for two years, giving AKT holders a defined period to complete the conversion. The token would move to the new network at a one-to-one ratio, retaining the same ticker and six decimal places. The plan says tokens sent to the portal would leave circulation on Cosmos, so the total supply would not change. These conditions tie the token’s use on Solana to completion of the audits, while the transfer portal would remain open after launch for the period set out in the plan.
The proposal separates the token migration from the move of the Akash marketplace and sets no date for transferring the market to Solana. That date would come through a separate governance vote, proposed only after the market audits and migration tests are passed. Four governance proposals would govern the move, beginning with the migration proposal, followed by a proposal to set the conversion date, then an upgrade to halt the old chain 21 days before the conversion and another upgrade to halt it 21 days before the scheduled date. Once the market moves, the plan expects existing workloads to continue for 90 days so tenants can redeploy them. The plan said workloads “continue running for 90 days after the conversion while tenants redeploy them.”
The team cited a reduction in operational burden among the reasons for choosing Solana, noting that about 100 validators bond AKT to secure consensus and that the core team maintains forked versions of software components for the Cosmos chain. The team estimates that network fees to run the entire marketplace on Solana would be about 0.075 SOL per day under its design and current activity levels. It also estimated Akash marketplace transactions at about 15,000 per day, compared with 112M transactions per day by Solana users, and described marketplace activity as a small share of network volume. The team presented these figures to explain Solana’s operational and cost fit, not as a timetable or guarantee that the move will take place. In return, the plan says Akash would give up consensus sovereignty, validator revenue, native connectivity through IBC, and the narrative of operating an independent chain.
The network choice followed a broader research process that began on 15 December 2025, when Akash asked layer-one networks to submit options for providing shared security. The team then expanded the research into a cross-chain migration program, published by Overclock Labs on 10 August 2026 in 15 documents comparing seven options against 15 strict requirements. Performance criteria included sustainable capacity of at least 50 marketplace transactions per second and 500 transactions during peak periods, alongside median costs no higher than $0.01 and 99.5% availability over 24 months. The team said the EVM path was a finalist, citing its advantages in developer tooling and Cosmos links, while it viewed Solana as a fit for operational requirements under pressure and the absence of a single operator. The choice therefore followed a disclosed comparison of performance and operational criteria, rather than the Alpenglow upgrade; the plan cites instability in that upgrade as a factor that could lead the team to change its choice.
The plan includes tests for risks arising from differences in escrow behavior, possible exploitation of the migration portal and declining validator participation. Proposed verification measures include replaying the escrow history recorded on akashnet-2 on the new programs, using more than 500 test cases and running intensive tests to verify invariants. These tests are among the conditions that must be met before a vote on moving the market, alongside its audits and migration trials. The project’s operational context includes the BME mechanism, which entered the mainnet on 23 March 2026 after proposal 318 was approved; Akash says it links demand for computing to demand for AKT. The company’s report for the first quarter of 2026 also said cumulative spending on computing exceeded $5 million during the first 90 days of the year. The next step specified in the plan is a vote on the migration proposal; no date for moving the market is set before the audits and trials are completed and a separate vote is held.