Offline signing and durable nonces solve different problems. Offline signing keeps a private key away from the internet; it does not extend a transaction’s validity. A normal Solana transaction still depends on a recent blockhash and can expire while signatures are being collected. A durable nonce substitutes a stored nonce value for that recent blockhash, allowing a signed transaction to wait longer—but the nonce is shared state that can be advanced or consumed before submission. As of October 2026, durable nonces are planned for deprecation but remain supported, with no final removal date.
Offline signing and durable nonces are not the same feature
Think of a Solana transaction as a fixed message that every signer approves. The message includes the fee payer, accounts, permissions, instructions, instruction order and a transaction-lifetime value. That lifetime value is normally a recent blockhash; with a durable nonce transaction, it is the value stored in a nonce account.
As an Amazon Associate I earn from qualifying purchases.
- Offline signing describes where the private key operates. A device can construct and sign the exact message without connecting to the network. A separate connected device or coordinator can later transmit the signed bytes.
- A recent blockhash gives an ordinary transaction a short processing window. The transaction pipeline documentation describes a 150-slot processing-age limit for recent blockhashes. Once the blockhash ages out, the signed message must be rebuilt and signed again.
- A durable nonce is an on-chain value stored in a nonce account and used instead of a recent blockhash. It can keep a transaction usable beyond the recent-blockhash window, provided the nonce has not been advanced and every other validation condition still holds.
Therefore, you can sign a Solana transaction offline without using a durable nonce. A nonce becomes useful when an offline or multi-party process may take longer than the recent-blockhash window, or when a business workflow needs an explicitly managed transaction-lifetime value.
Recommended Free Tools
“For workflows that may take longer or include offline signers, use a durable nonce.” — Solana Documentation, Partial Signing
#1 Best Overall
Can I sign a Solana transaction offline without using a durable nonce?
Yes. The signer can receive a fully prepared transaction, verify its details on an offline device, and return a signature. The connected party then submits the signed transaction. The important limitation is that an ordinary transaction’s recent blockhash continues aging while the device is offline or while other parties are signing.
What must happen before the blockhash expires
- A connected coordinator fetches a recent blockhash and constructs the complete transaction.
- The coordinator distributes the exact serialized message to each signer.
- Each signer verifies the fee payer, destination accounts, permissions, amounts and instruction order before signing.
- All signatures are collected without changing any byte of the message.
- The fully signed transaction is submitted and monitored before the blockhash leaves the validator’s recent-blockhash queue.
If the blockhash expires at any point, adding a fresh blockhash to the old signed transaction is not a repair. The blockhash is part of the signed message. Replacing it changes the bytes, so every required signature must be collected again.
Hardware devices and other offline signers can sign the same message bytes as an online signer, but compatibility is implementation-specific. Confirm that the wallet, device, SDK and transaction format you intend to use can display and sign the transaction before relying on an air-gapped procedure. The general signing model is described in Solana’s Partial Signing documentation.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
How a durable nonce transaction works
A durable nonce account is owned by the System Program. Once initialized, it stores an authority public key, a durable nonce value and the lamports-per-signature fee rate recorded when the nonce was last advanced. The nonce value becomes the transaction’s lifetime value.
1. Create and initialize the nonce account
The account must be created and initialized with an authority. That authority is the signer permitted to advance the nonce. Account creation and maintenance require SOL for the account’s rent-related balance and transaction fees; the exact amount depends on current network rules and the account size, so use the current Solana CLI reference or your wallet’s current interface for live values.
2. Fetch the current stored nonce
The coordinator reads the nonce account and obtains its current value. Treat that value like a one-use reservation: another transaction or operator that advances the same account can make a saved transaction unusable.
Rank #2
- Ideal for Gifting
- Ideal for a bookworm
- Compact for travelling
3. Put AdvanceNonceAccount first
A durable nonce transaction is identified by its first instruction. The first instruction must be AdvanceNonceAccount, and the transaction’s recent_blockhash field is set to the stored nonce value. The nonce authority must sign. Other application instructions follow in the order required by the workflow.
4. Freeze the complete message before signing
Every signer must approve the same serialized message, including the fee payer, nonce value, account metas, permissions, program IDs, instruction data and instruction order. A change to any of these fields creates a different message and invalidates signatures collected for the earlier version.
5. Sign offline and transfer the signed bytes
The nonce authority and any additional signers can sign without network access. Use a verifiable transfer method to move the signed transaction to a connected submitter. The submitter should not “refresh” the nonce, fee payer or blockhash field after signatures are attached.
6. Submit while the nonce still matches
Validators check that the nonce account is initialized, that its stored value matches the transaction’s lifetime value, that it can advance and that the nonce authority signed. When those checks pass, the nonce advances before the remaining instructions execute. Fetch the new nonce before preparing another transaction.
The complete protocol details, including account state and validation, are in Solana’s Durable Nonces documentation.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Recent blockhash or durable nonce for offline signing?
| Question | Offline signing with a recent blockhash | Offline signing with a durable nonce |
|---|---|---|
| What does “offline” describe? | The private key signs away from the internet; a connected device later submits the signed transaction. | The same separation between signer and submitter. |
| What sets the lifetime? | The validator’s recent-blockhash queue; current pipeline documentation describes a 150-slot processing-age limit. | The stored nonce remains usable until it is advanced or otherwise no longer matches. |
| What must be coordinated? | All signers must return before the recent blockhash expires. | The nonce account, nonce authority and nonce value must remain valid and unconsumed. |
| What does each signer approve? | The exact message, including the recent blockhash and fee payer. | The exact message, including the durable nonce and fee payer. |
| What invalidates pending signatures? | An expired blockhash or any change to the signed message. | An advanced or consumed nonce or any change to the signed message. |
| What happens after a failure? | An expired message needs a new transaction and a new signing round. | A validation failure is dropped without fees or state changes; an execution failure after nonce validation still advances the nonce and charges fees. |
The nonce option extends the coordination window, not the security of a careless workflow. Anyone who can advance the nonce account can invalidate a saved transaction based on the old value, so nonce authority must be controlled as carefully as the signing key.
How long does an offline-signed Solana transaction remain valid?
With an ordinary recent blockhash
Validity lasts only while the referenced blockhash remains within the validator’s processing-age window. Solana’s current transaction-pipeline documentation describes that limit as 150 slots. Slot duration and network conditions can vary, so do not convert that figure into a guaranteed number of seconds. If a signing ceremony, approval queue or transport delay may exceed the window, plan to rebuild the transaction rather than hoping the original signature remains usable.
With a durable nonce
A nonce-based transaction can wait beyond the recent-blockhash window, but it is not valid indefinitely. The stored nonce must still match the transaction, the nonce account must remain initialized, and the authority signature and other transaction checks must pass. Once the nonce is advanced, the old value cannot be reused for another submission.
What happens if a Solana durable nonce transaction fails?
There are two materially different failure points.
Validation failure
If the validator rejects the transaction during validation—for example, because the nonce account is not initialized, the stored nonce does not match, the nonce cannot advance or the required authority signature is missing—the transaction is dropped. In this case, no transaction fee is collected and no nonce or application state change is committed.
Execution failure after nonce validation
If validation succeeds, the nonce advances before the later instructions run. A subsequent instruction can still fail because of a program error, a permission problem, insufficient funds or another runtime condition. The nonce advancement and fee deduction remain committed even though the intended application action did not complete. The old signed transaction cannot simply be resubmitted: its nonce has already been consumed. Fetch the current nonce, decide whether any partial state change occurred, rebuild the transaction and collect signatures again.
This distinction is why nonce workflows need explicit monitoring. Record the transaction signature, inspect confirmation and program logs, and reconcile the nonce account after every submission rather than treating a failed application instruction as a free retry.
Keeping an offline signing ceremony safe
Freeze and verify the message
- Display the fee payer and every account that can receive funds or authorize an action.
- Verify instruction order, program IDs, amounts, token mints and authority relationships.
- For a nonce transaction, verify that
AdvanceNonceAccountis the first instruction and that the displayed nonce equals the value fetched from the nonce account. - Use the same serialized message for every signer; never edit a partially signed transaction to change fees, accounts or lifetime values.
Separate signing from submission
The offline device should receive only the data needed to verify and sign. A connected coordinator can broadcast the resulting bytes, but it should not have access to the private key. Protect transfer media and verify checksums or transaction encodings according to the wallet or SDK procedure you have selected.
Rank #4
Plan for expiry and nonce contention
For a recent-blockhash transaction, set a deadline for collecting signatures and submitting. If that deadline is missed, discard the old partially signed message and start with a new blockhash. For a nonce transaction, reserve the nonce operationally: do not let another operator, automation job or recovery process advance the same account while signatures are pending.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchCheck the exact device and software combination
General documentation establishes that offline and hardware signers can sign Solana message bytes, not that every retail device supports every instruction, address format or nonce flow. Test the precise wallet, firmware, SDK and transaction type with a small-value operation before moving production funds.
What ordinary wallet users need to do now
Most users do not need to change anything solely because durable nonce deprecation is being discussed. The Solana Foundation says wallets and apps continue to work as before and that action is needed only for people who personally use durable nonces. If a custodian or service uses nonces on your behalf, that provider is responsible for its migration plan.
If you are setting up offline signing for occasional transfers, start with an ordinary recent-blockhash transaction when your approval and submission process fits inside the processing window. Consider a durable nonce only when the workflow genuinely needs a longer coordination period or a managed nonce account. Confirm support in the exact wallet and signing device before transferring significant funds.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Are Solana durable nonces being deprecated?
Yes, deprecation is planned, but it is not an active removal and it has no final calendar date as of October 2026. The Solana Foundation labels the work “In Development.” Its stated plan is to keep current nonce transactions valid until a replacement is audited and live on mainnet, with removal expected roughly six months after that replacement is ready. That is a plan, not a scheduled network activation.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problems“Only if you use durable nonces.” — Solana Foundation, Durable Nonce Deprecation, describing which users are affected.
Best Value
Sale
I Will Teach You to Be Rich: No Guilt. No Excuses. Just a 6-Week Program That Works (Second Edition)
- It can be a gift option
- Comes with secure packaging
- Helpful in various ways
Ordinary recent-blockhash transactions are not being deprecated as part of this change. Teams that operate nonce-based custody, settlement, relaying or approval systems should track the Foundation’s upgrade page and test a migration path well before any announced activation.
What replacements are being developed?
The Foundation identifies two candidate approaches: Anza Programmatic Signer and Blueshift Vector. Both move offline signature checking and replay protection into on-chain programs instead of relying on validator-runtime nonce special cases. Their execution paths use cross-program invocation (CPI) and a signer program-derived address.
- Anza Programmatic Signer: the Foundation reports an implementation on Devnet. It uses a standard v1 message payload and supports multiple authorities. The page says audits precede an Anza v1 release; it does not present a finished, audited mainnet replacement.
- Blueshift Vector: its signature covers every top-level instruction and it supports additional signature schemes listed on the Foundation page. The page describes the implementation and interface as developing and does not state that Vector has completed an audit.
The designs differ in the data covered by the offline signature, whether a relayer can add instructions around the signed payload, supported signature schemes, nonce-account structure and CPI stack depth. Both require authorized instructions to execute through CPI. That can matter to applications that require top-level instructions or enforce CPI guards. Do not migrate production logic to either design until its interface, audit status, mainnet availability and application constraints are confirmed.
Why the Foundation is changing the nonce design
The Foundation’s upgrade explanation reports figures attributed to SIMD Discussion #564 for one June 2026 epoch: durable nonce transactions represented 3.1% of transactions but 30% of priority fees paid, and 555 fee payers sent 97.5% of those durable nonce transactions. These are the Foundation’s cited figures for its rationale concerning spam and fee concentration, not a universal share for every epoch or application.
For a normal wallet user, the practical implication is limited: ordinary transactions continue to use the standard recent-blockhash path. For a custodian or developer, the implication is architectural. A replacement may change how signatures are structured, how relayers add instructions, how replay protection is enforced and how much CPI stack depth an application consumes.
Operational choices for advanced teams
When a recent blockhash is the better fit
- The signing round is short and all parties can coordinate inside the 150-slot processing-age window.
- The application does not need a transaction to wait for a human approval queue or an offline transport delay.
- You want to avoid nonce-account lifecycle management and nonce contention.
When a durable nonce can still be appropriate today
- Multiple signers are geographically separated and cannot reliably return signatures quickly.
- An offline approval process intentionally keeps the signing device disconnected for longer than a recent-blockhash window.
- Your existing production system already manages nonce authorities, replay handling, fee accounting and recovery procedures.
Controls a production signer should add
Production systems should isolate keys, restrict who can advance nonce accounts, log the exact message hash and nonce value, and reconcile on-chain state after submission. Solana’s guidance on signer architectures and key-management backends is available in Signing in Production. Managed key-management, hardware security module and multi-party computation designs can protect keys, but they do not remove the need to understand blockhash expiry or nonce consumption.
Recovery checklist
- Recent blockhash expired: discard every partial signature, fetch a new blockhash, rebuild the message and obtain all signatures again.
- Nonce was advanced first: treat the saved transaction as unusable, fetch the current nonce and create a new message.
- Nonce transaction failed during execution: assume the nonce and fee were consumed, inspect logs and state, then rebuild with the current nonce.
- Signer changed a field: stop collecting signatures for the old message and restart; signatures cannot be transferred to an edited transaction.
- Device cannot display an instruction: do not sign blindly. Verify support for that transaction type or use a tested signing path.
For protocol-level details, consult Durable Nonces, Partial Signing and Transaction Pipeline in the Solana documentation. Recheck the Foundation’s deprecation page before changing a production workflow, because replacement designs and timing remain subject to development and governance decisions.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
