Akash Network, the decentralized cloud-computing marketplace, is holding one of the most consequential votes in its history — a proposal to abandon its sovereign Cosmos chain and migrate the entire AKT token and marketplace to Solana. But buried in the proposal’s fine print is a detail that should make every AKT holder sit up: the migration would end the inflation-funded staking rewards the chain pays today, while explicitly leaving the door open to issuing new tokens for other purposes.
Proposal 346 remained in voting as of November 2, with a deadline of 15:02 UTC the same day. A successful vote would authorize the migration and a one-way token portal, while leaving the marketplace’s actual cutover date to a future proposal. The stakes for holders are captured in one line of economic logic: a promise to exchange one old AKT for one new SPL AKT preserves your balance at conversion — it does not preserve the income attached to staking that balance.
What ends, and when
The proposal separates the migration into distinct phases, each with its own consequences. Old-chain inflation and staking rewards would end at cutover, when the marketplace moves. Validator roles and income would end 90 days later, at the old chain’s halt. SPL AKT and the one-way portal are expected to launch two to three weeks after passage, once token and portal audits complete.
Even the user flow is unsettled. The submitted proposal describes a portal transaction that starts unbonding, claims rewards, and queues migration after 21 days. But an October 20 technical draft used seven days to token launch and 14 days for unbonding, while an October 26 blog post said two weeks to launch and 21 days of unbonding. Final audited instructions will have to reconcile all three versions — a reminder that this is a moving document, not a finished manual.
Greg Osuri, Akash’s founder, has said new staking mechanisms will be announced before cutover. That is a commitment to explain a replacement yield — not a published payout formula. Holders voting today are approving a framework in which the terms of their future income do not yet exist.
New issuance, just not for you
Here is where the economics get pointed. Akash’s AEP-79 migration design makes separate provision for replacement emissions: newly issued AKT directed to provider incentives and the community treasury. The design describes reduced gross emissions as the intended direction, but leaves the actual curve — the rate, decay, recipient split, and cumulative hard cap — to future modeling and governance.
Read that carefully. A holder could lose the present inflation-funded staking income while new tokens continue to be issued for other purposes. Issuance to providers and the treasury expands the token base without automatically increasing a passive holder’s balance. The dilution and the yield don’t cancel out — one ends, the other continues elsewhere.
There are guardrails. The cumulative incentive-emissions cap, once set from the ratified model, could not be raised by governance, and a guardian can pause emissions. The draft even allows a paused start: if the model isn’t ratified before the cutover supply snapshot, the issuance program would begin with zero scheduled emissions. But the numerical ceiling, emission rate, and start date are all unresolved today.
The compute-credit accounting puzzle
Supply questions extend to Akash’s compute payments. The AEP-76 roadmap describes ACT as a nontransferable, dollar-denominated compute credit funded through a burn-mint equilibrium, and its vault model permits minting a shortfall if previously removed AKT is insufficient. The proposed Solana architecture, by contrast, expressly forbids the burn-mint program from minting AKT, keeping collateral in a vault instead. Two documents, two different limits — and the reconciliation is still an open implementation question.
The distinction matters for anyone counting on deflationary pressure. Tokens locked in a vault are temporarily removed from trading, not permanently destroyed, and whether compute usage creates net burn or net issuance depends on which accounting model wins.
What holders should watch
The portal, if approved, would stay open for two years, and migration is irreversible. The proposal does require the emissions curve to be published before the cutover vote, alongside the promised staking details — which means holders will get one more chance to judge the post-migration economics before the marketplace actually moves.
For AKT investors, the checklist is short. Did Proposal 346 pass, and by what margin? What do the final audited migration instructions say about unbonding windows? And most importantly, what does the emissions curve look like when it’s finally published — because that document, not this vote, will decide whether holding AKT after the migration is a yield position or just a bet on the marketplace’s growth. Solana’s speed and liquidity are a genuine upgrade for a compute marketplace. But migrations like this redistribute value as much as they create it, and the fine print is where it happens.
so balances survive the move to SPL but staking income just dies at cutover while fresh AKT keeps printing. holders eat the transition costs, glad i unstaked last month
same boat. also that 2-3 week gap between passage and SPL AKT launching sounds like a chaos window for the old token price
One-way portal, audits still pending, validators retired 90 days after cutover. Reasonable sequencing on paper, but the vote timing matters more than any of it.
proposal 346 kills staking inflation but keeps fresh issuance on the menu for whatever comes next. i voted no on chains i cared less about, at minimum wait for the audit before approving a one way portal
1:1 swap preserves your bag and kills your yield, neat trick. proposal 346 reads like staking rewards are collateral damage nobody wanted to say out loud
1:1 on the balance sheet while the income column goes to zero is the finest print in proposal 346. and new issuance staying on the table makes it worse
the new issuance line is the part nobody prices. staking income dies at cutover but reserve printing somehow survives the rewrite. wild set of priorities for a proposal sold as a clean move
imagine validating for years and the migration roadmap thanks you with 90 days notice lol
ninety days of runway after years of signing blocks. the migration roadmap treats validators like office furniture
vote deadline at 15:02 utc with audits still pending is doing a lot of work here. holders are approving a one-way portal before anyone signed off on the destination
audits after the vote is backwards sequencing. you approve the one way portal first and read the safety report on the destination later. holder apathy will carry it anyway
backwards sequencing is the generous read. the less generous one is they suspect the audit lands messy and want the one way portal approved before holders get a chance to react to it
Watched this movie with other cosmos migrations. Validators get 90 days of income then nothing, holders get a token with reduced security budget. Good luck to them.
monthly akt rewards were covering my server costs. now i get to redeploy hardware to a chain where my cut is zero. the migration math only works if you ignore the people actually running the machines
same, my akt payouts covered colo costs for two years. the plan asks operators to keep machines running on a chain whose rewards clock stops at cutover. who secures the marketplace during that 2-3 week gap before SPL akt even exists