Wallet custody, cryptographic trust boundaries, vulnerabilities, audits and practical defensive habits

Solana Durable Nonces: What an Offline-Signing Replacement Would Change

If you use offline signing to keep a cold key separate from the wallet that submits transactions, Solana’s expected removal of durable nonces raises a practical question: how would that separation work afterward?

An article published on November 13, 2026, at 18:43 (UTC+8) explains why durable nonces are slated for removal. It says their special runtime logic creates a replay vulnerability, blocks asynchronous execution and can be exploited through spam transactions during congestion. These are the article’s stated reasons for the change, not a report of a specific loss.

The article describes an alternative: an on-chain offline-signing program using a CPI Passthrough pattern. A cold key signs offline; a hot wallet pays the fee and submits the transaction. The program then verifies the signature and advances its own nonce. This preserves a distinction between the key authorizing an action and the wallet submitting it, though the article does not present the pattern as eliminating custody risk.

The article compares Anza Programmatic Signer and Blueshift Vector across signature coverage, hardware-wallet compatibility, key types, PDA management, concurrent messages and tooling. It also walks through an offline SOL transfer with each. Its migration discussion flags program compatibility—including stack height, instruction introspection and Token-2022 CPI Guard—as well as remaining work. Anyone evaluating a move away from durable nonces would need to check those compatibility questions for their own application rather than assume the two approaches are interchangeable.

Further reading