Solana Plans Durable Nonce Retirement as Offline Signing Moves Onchain

The Solana Foundation has outlined a plan to retire durable nonce transactions and move offline authorization into onchain signer programs. Durable nonces remain available today, and the Foundation has not selected a final replacement or fixed a shutdown date. The stated direction is to keep the current system until a suitable replacement is audited, deployed on mainnet and given a migration period of roughly six months.

The change matters most to exchanges, custodians and treasury operators that cannot complete approvals within the short life of a normal blockhash. A standard Solana transaction is tied to a recent blockhash that remains valid for 150 slots. A durable nonce replaces that expiring value with stored account state, allowing a transaction to be signed offline and submitted later.

Why Solana wants to change the model

Durable nonces require special runtime rules. Validators must identify the nonce account, verify its stored value, advance it before execution and preserve the advance even if a later instruction fails. That behavior prevents replay, but it also adds account-dependent validation and scheduler complexity.

The proposed replacement moves signature verification and replay state into ordinary onchain programs. A cold key would sign an authorization message, while an online operator would place that authorization inside a fresh-blockhash transaction and pay the network fee. Readers who follow the asset can view SOL spot trading on OrangeX.com or SOL perpetual markets on OrangeX.com; trading access does not indicate that a protocol change is active.

Two candidates, no final choice

The Foundation identifies two leading implementations: Anza's Programmatic Signer and Blueshift's Vector. Both aim to preserve offline approval while moving execution through a program-derived authority. Their message formats, account setup and control over surrounding instructions differ, so wallets and institutional operators will need to assess the final design rather than assume the candidates are interchangeable.

Retry behavior is another material change. Under the current durable nonce flow, a transaction that passes nonce validation but fails during execution still advances the nonce and charges the fee payer. In the proposed program-based model, a failed attempt can leave the signed authorization valid for another submission. That may improve reliability, but it also means operators need explicit deadlines, nonce revocation procedures and controls against delayed execution.

What users should watch next

There is no immediate action for ordinary SOL holders. The current mechanism remains usable, and the replacement still needs a final selection, audits, mainnet availability, wallet tooling and application compatibility. Institutional users should inventory every authority and workflow that relies on durable nonces, including token, stake and treasury permissions. Updates can be followed through OrangeX.com Crypto News.

OrangeX.com Analysis

The proposal is a redesign of authorization infrastructure, not a routine parameter change. Moving replay protection out of the runtime can simplify validator behavior, but it transfers more responsibility to signer programs, wallets, relayers and operational policy.

The key uncertainty is implementation readiness. The migration window is an expectation conditioned on an audited mainnet replacement, not a confirmed countdown. Until a final design and activation schedule are published, the defensible conclusion is that durable nonces are marked for retirement while their successor remains under evaluation.