Akash approves a 1:1 AKT move to Solana: check the token window before transferring

Approval settles the direction, not every transfer instruction

The November 3 report describes approval to leave the independent Cosmos chain, akashnet-2, and issue AKT on Solana after the token and portal audits. It reports approximately 97% support. PANews separately reported the community-backed move and the planned 1:1 exchange into SPL AKT, attributing its report to Tech in Asia. PANews's account.

That is relevant to anyone who holds AKT on an exchange or in a wallet. A change of home chain changes which instructions matter when assets are moved. A ticker alone cannot answer whether a receiving account supports the old-chain token, the Solana token, or both. Treat those as separate questions for the account where you intend to receive funds.

Akash's October 26 explanation supplies the proposed sequence. The token moves first; marketplace operations follow after development, audits and rehearsals. The report names Akash Marketplace, AkashML and Homenode as the services intended to run natively on Solana.

The two clocks in the headlines

PANews describes the broader infrastructure move as taking place within 24 months. Akash's own plan describes a two-year token portal beginning at launch and says marketplace cutover has no date yet. These statements should not be collapsed into a single countdown for a holder. The project's operational instructions are the useful starting point for a transfer decision.

These are conditions from the plan, not evidence that any stage beyond the reported approval is already complete. Akash's explanation mentions a token launch roughly two weeks after approval, while ChainCatcher describes an expected two-to-three-week period. Neither estimate establishes that the audits have passed. Keep the audit condition attached to the time estimate.

For a calendar reminder, save the launch date once Akash publishes it. Starting a two-year clock from a news headline would create the wrong deadline. Equally, a long portal window does not remove the need to read later instructions, especially if your tokens are staked or held through another chain.

If your AKT is on an exchange

Akash's holder instructions say exchanges move customer balances through the portal on their own schedules. The plan does not give a universal conversion date for every venue. It also identifies slow exchange migration as a risk because old-chain and new-chain versions could trade alongside each other and split liquidity.

1. Before a deposit or withdrawal, open the specific AKT asset page for your account. Read the network name, whether transfers are enabled, and any migration notice attached to it. Record what the page says rather than assuming that a supported AKT market also accepts every AKT network. A trading pair and a deposit route answer different questions.

2. If a venue announces automatic handling, read which balances it covers and whether there are temporary transfer changes. If it has not provided instructions, the project-wide vote alone cannot tell you how that venue will process your balance. This run did not verify an individual exchange's support for SPL AKT, a suspension time, a conversion schedule or a withdrawal fee.

3. Keep a record of pending AKT transfers before making another one. Note the sending account, receiving account, selected network and transaction status. These are practical comparison fields, not a claim that any exchange currently requires a particular action. The next useful piece of evidence is the migration instruction for the place holding your coins.

If you hold the tokens yourself

The project's plan describes connecting a Cosmos wallet to the migration portal and choosing a Solana receiving address. AKT migrates at 1:1. The move is one-way: migrated AKT cannot be moved back to Cosmos through that portal. Akash also says the old-chain tokens sent into the portal leave circulation, so the planned migration does not increase total supply.

A 1:1 token conversion describes token quantities. For example, a migration of 100 AKT would yield 100 SPL AKT under that ratio. It does not establish a cash payout, the same market price on two venues, or a profit. Save the token amount separately from any price you use to value the position.

The plan retains the AKT ticker and six decimal places. That continuity makes reading the network especially useful: the familiar symbol will not by itself identify the chain. Once operational instructions are published, compare the receiving address and selected network with them before confirming anything.

Akash calls phishing the main holder threat and says there will be one official portal domain. No portal address is supplied in this article because the sources opened for this run do not establish a live, audited portal. Return to the project's own explanation for the announced process. A message offering to migrate tokens is insufficient evidence of authorization.

Staked tokens and IBC balances need a different preparation step

For staked AKT, the official plan says tokens must first be unbonded, which takes 21 days, before using the portal. It also says staking continues to secure the old chain, earn rewards and participate in remaining votes until cutover. Old-chain inflation and those staking rewards are planned to end at cutover.

That sequence matters if your wallet balance is delegated. A liquid balance and a staked balance do not have the same preparation path in the plan. Check your delegation status before scheduling a migration. A vote passing does not, by itself, mean every holder should begin unbonding immediately; the portal launch and marketplace cutover remain distinct stages.

For AKT on Osmosis or another IBC chain, Akash's plan says to return the tokens to akashnet-2 before using the portal. This is a stated route in the project plan, not confirmation of the current transfer status of an individual IBC channel. Check the actual sending and receiving services before initiating a movement.

Akash also distinguishes Console-managed wallets, for which the plan says balances migrate automatically. Identify who controls your wallet before following self-custody instructions. A managed-wallet balance, an exchange balance and a delegated self-custody balance each have their own stated handling.

The compute marketplace follows later

AKT holders do not need to study every provider software change to understand the next decision. The useful distinction is that launching a token does not launch the entire marketplace. Akash says live workloads remain unchanged until cutover, and existing leases can continue until users close them or the old chain halts during the planned wind-down.

For readers who also buy compute, the project says existing SDL deployment files remain usable, while new deployments move to Solana at cutover. The plan sets a 90-day period between that switch and the old-chain halt. It also treats post-cutover top-ups differently from earlier deposits, so tenants should read the detailed account instructions before adding funds to old-chain leases.

Those details explain why the separate cutover vote matters to a retail holder. The token conversion window and the marketplace's operating schedule are connected, but they are not interchangeable deadlines. An exchange can need one set of instructions for token balances while a compute customer needs another for leases.

Akash presents lower operating costs, access to liquidity and existing decentralized-infrastructure activity on Solana as reasons for the choice. Those are the team's rationale. They do not establish a future AKT price, new exchange availability or a holder's trading return.

What is still missing before a holder acts

The official explanation leaves open how unvested AKT migrates, how tokens still on Cosmos at halt reach the portal, and what happens to tokens not migrated within two years. These are material questions for affected holders. Do not fill them with an assumed extension, recovery service or automatic conversion.

This run verified the project plan and opened contemporary approval reports. It did not verify completed token audits, a portal launch, a live SPL mint address, an exchange conversion notice or a marketplace cutover date. The next check is concrete: match a subsequent official instruction to the location and status of your own AKT balance.

Market tools: funding board and liquidation board.

Quick answers

Does the two-year window begin with the vote?

Akash's plan says the portal remains open for two years from token launch. The launch is conditional on two independent audits. The approval report does not establish a completed launch.

Is 1:1 a return on my investment?

It is the planned conversion ratio between AKT and SPL AKT. One hundred old-chain tokens would become one hundred new-chain tokens under that ratio; the sources do not promise a market value.

Will an exchange automatically convert every balance today?

The project says exchanges handle customer balances on their own schedules. No individual venue's current conversion instructions were verified for this article.

Can I send migrated AKT back through the portal?

The published plan describes a one-way move from Cosmos to Solana. It does not provide a reverse migration route.