Akash opened voting on October 26 for Proposal 346, which asks stakers to authorize moving the protocol from its Cosmos chain, akashnet-2, to Solana mainnet. The public governance record checked on October 27 still listed the proposal as being in its voting period, with voting scheduled to end November 2 at 15:02 UTC.
The proposal text and status separate three milestones: approval of the migration, a later AKT token launch, and an eventual marketplace cutover. Passage would authorize the token launch after the specified audits. It would not itself set a cutover date or move the compute marketplace.
That separation matters for providers and tenants. The proposal says existing leases, staking and governance continue on akashnet-2 until the relevant transition steps. Moving the marketplace requires audits, migration rehearsals and another proposal approving the cutover. A favorable early tally therefore cannot establish either a final governance result or a completed deployment.
In its October 26 announcement, the core team describes rebuilding the marketplace as native Solana programs. Its documented plan keeps tenants' SDL deployment files unchanged while requiring changes to provider software and registration. Those are proposed migration arrangements, rather than an upgrade that operators can treat as already shipped.
The client boundary also changes in the plan: a new SDK release and Console API version would use Solana-facing interfaces, while the existing API version would retain old-chain data. Integrators need to distinguish that planned interface work from the chain that currently serves their deployments.
Solana Compass's report also distinguishes the open vote from a later marketplace decision. The immediate development is the governance process opening. A token-launch announcement, completed audits and a separately approved cutover remain distinct evidence to watch for.