Akash Picks Solana for 1:1 AKT Move as Vote Opens

Akash’s Solana vote runs through November 2

The Proposal 346 record sets the voting window from October 26 to November 2 at 15:02 UTC. A direct check of Akash’s public chain data around 05:03 UTC on October 27 still returned an open voting period.

That check showed about 43.74 million AKT voting yes and 708,000 voting no, alongside smaller abstention and veto totals. These were provisional votes, not a finalized governance result. Token holders can change their positions before the deadline.

The submitted proposal text reproduced by validator Polkachu requires 33.4% quorum and majority support. It explicitly separates authorization of the token from the later marketplace cutover, which has no scheduled date.

This distinction avoids treating a favorable running tally as a completed chain migration. It also identifies two separate execution risks: moving holders’ balances and moving the commercial system that matches computing customers with providers.

Other networks have confronted similar choices over dedicated infrastructure. GnosisDAO’s approved Ethereum L2 shift likewise separated a governance mandate from subsequent technical deployment and validator changes.

AKT’s one-way swap has no fixed launch date

Under Proposal 346, holders would receive the same quantity of SPL AKT, Solana’s token format, with the existing ticker and six decimal places preserved. Tokens converted through the portal would leave circulation on the old chain. The proposal provides no reverse conversion.

The portal would remain available for two years from token launch. Staked balances would retain a 21-day unbonding process, and exchanges would migrate customer balances on their own schedules. Those conditions mean one holder’s transition need not coincide with another’s.

The timetable needs clarification. The proposal estimates launch two to three weeks after passage and completed audits; the announcement says two weeks. The project’s token-migration design draft, dated October 20, instead describes seven days after the voting period ends.

Those intervals cannot all serve as one confirmed calendar. The draft remains labeled for review, and an estimated interval is not an announced launch date. Holders would need the final official instructions before assuming a Solana balance is available.

The draft’s supply-accounting framework requires correspondence between old-chain tokens removed and new tokens minted, with reconciliation and a pause if balances disagree. That is a proposed control, not a published finding that the eventual portal has passed its audits.

Cloud workloads await a separate Akash cutover

The proposal keeps live leases, staking and governance unchanged before cutover. After a separately approved transition, existing workloads would have a 90-day old-chain operating window while customers redeploy. Providers would update software and register on Solana.

For tenants, token conversion and service continuity answer different questions. Owning the replacement asset would not itself confirm that a workload has been redeployed or that its provider is ready. Businesses would still need to coordinate operational changes with their hosting arrangements.

Akash’s rationale fits the broader DePIN effort to sell real infrastructure services through blockchain networks. Helium’s reported mobile-data offload activity offers another example of why customer usage and blockchain architecture must be assessed separately.

The proposal also identifies unfinished terms, including treatment of AKT left after the two-year portal window and the eventual emissions curve. These affect holders’ economic position beyond the headline conversion ratio and remain subjects for later disclosure.

Alternative.me’s Bitcoin-focused sentiment gauge read 48, or Neutral, on October 27, down from 50 a day earlier. It supplies broader market context rather than measuring confidence in Akash’s proposal.

The next concrete checkpoint is the November 2 vote close. A final result, published audit reports and reconciled launch instructions would establish whether token migration can proceed; the marketplace’s cutover date remains a separate decision.