Builders on decentralized compute are watching Akash Network's chain handover this week: the one-way AKT migration to Solana is live with mainnet contracts deployed, the first concrete step after governance approved the move on November 2. The marketplace itself has not moved yet, and that second cutover is where provider billing actually changes.
Key facts
- Mainnet bridge contracts are deployed and documented, with transfers runnable through a web portal (Keplr login) or the
akt tx sink depositCLI on akt v1.1.1. - Transfers are one way: AKT minted on Solana cannot return through Akash Migrate, and each transfer completes in minutes via relayers plus a reporter vote exceeding two thirds.
- Prop 346 passed on November 2, 2026 with 97.27% of votes cast in favor, after opening October 26; about 888,000 AKT abstained and roughly 765 AKT voted NoWithVeto.
- The migration is liquidity-first: Prop 346 authorized the 1:1 SPL token and portal, while moving the compute marketplace requires a separate cutover vote.
What's driving the conversation
The migration has been a running topic across decentralized-inference circles since Akash announced the Prop 346 result on X, telling followers "Prop 346 has passed. Akash is coming to Solana. Same mission, bigger stage." The liquidity-first sequencing is what builders are picking apart: token holders can cross now, but the marketplace cutover that actually re-routes provider payments and tenant billing has no announced date.
That gap between token portability and platform migration is the honest center of the discussion. A GPU provider earning settlement in AKT today keeps earning it on the Cosmos chain until the second vote passes and executes. Renters, meanwhile, can hold SPL AKT weeks before that matters operationally.
The substance
Akash's migration documentation is the verifiable layer here, and it is specific. A deposit locks AKT in the sink module and writes a permanent record; a relayer submits Akash block headers and a proof to Solana, where the AKT program checks it against an Akash light client; Solana mints the recorded amount; independent reporters then settle the transfer on Akash by vote. Governance sets per-transfer, per-account, aggregate, and daily mint caps, and a failed Solana delivery triggers a refund on the Akash side.
What the docs do not state is a completion date for the marketplace cutover, or the outcome of the two audits gating the new chain's launch, which the team has cited as prerequisites. Both remain the team's stated plan rather than a guarantee, and the second governance vote has not been scheduled publicly.
Why builders are watching
Akash is one of the larger decentralized compute marketplaces serving GPU tenants, so its settlement layer is infrastructure for the same builders our decentralized inference coverage tracks. Billing, provider onboarding, and tooling all route through the token layer, which is why a chain move is operational news and not just token plumbing. The move also puts Akash in the same ecosystem as Solana's confidential compute work, which matters if private inference workloads follow the marketplace over.
Watch two things: the marketplace cutover vote, which is when provider economics actually change, and whether the audits clear on the timeline the team has described.
Questions
- What is Akash Migrate?
- Akash Migrate is the one-way transfer system that moves AKT from Akash's Cosmos-based chain to Solana. You lock AKT on Akash, a relayer proves the deposit to a Solana program, and the same amount of AKT is minted to your Solana wallet. Transfers cannot be reversed through the portal.
- Has the Akash marketplace itself moved to Solana?
- No. Only the token migration is live. Prop 346 authorized the 1:1 SPL token and the transfer portal; moving the decentralized compute marketplace itself requires a separate cutover vote, and staking rewards end only at that later cutover.
- Can AKT sent to Solana be sent back?
- No. Akash's documentation states transfers are one way. AKT that arrives on Solana cannot be sent back to Akash through Akash Migrate, though a failed delivery triggers a refund process on the Akash side.
Sources
- Akash Migrate: AKT on Solana — Akash Network docs
- Akash Network Votes to Move to Solana as Prop 346 Passes With 97% Support — Solana Compass
About DeAI
DeAI is an independent publication covering open-weight AI models, private inference, and decentralized infrastructure — the tools for running AI you actually control. We test providers on price, privacy, and refusal behavior and publish the numbers, not the vibes. DeAI is powered by Morpheus (mor.org), a decentralized inference marketplace, and covers it on the same terms as every other provider.
Powered by Morpheus and StrandCMS
Morpheus is a decentralized inference marketplace, covered on the same terms as every other provider — we rank it wherever the data lands. StrandCMS is the open-source, agent-first framework this site is built on.
