iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Offline signing and durable nonces solve different problems. Offline signing keeps a private key away from the network while a transaction is authorized. It does not extend the transaction’s lifetime. A normal Solana transaction signed offline still uses a recent blockhash and expires when that blockhash leaves the validator’s recent-blockhash queue. A durable nonce replaces that recent blockhash with a value stored in a nonce account, allowing a transaction to be signed offline and submitted later. The trade-off is that the nonce is shared state: once it is advanced or consumed, a saved transaction using the old value cannot be submitted again.
For most wallet users, ordinary recent-blockhash transactions remain the simplest choice. A durable nonce is useful when an offline, multi-party, custody, or approval workflow may take longer than the recent-blockhash window. As of October 2026, durable nonces are still active. The Solana Foundation lists their deprecation as In Development, with no final removal date; current nonce transactions are expected to continue working until a replacement is audited and live on mainnet.
What offline signing changes—and what it does not
In an offline-signing setup, one device constructs or receives the transaction message, a disconnected signer authorizes the exact bytes, and an internet-connected device or coordinator broadcasts the resulting signed transaction. The private key never needs to be exposed to the networked device. A hardware device or other offline signer can sign the same frozen message bytes described in Solana’s Partial Signing documentation.
Offline describes where signing happens. It does not describe transaction lifetime, replay protection, or whether a transaction can wait indefinitely. Those properties come from the lifetime value in the message: normally a recent blockhash, or, for a durable-nonce transaction, a stored nonce value.
#1 Best Overall
- Effortlessly build your crypto portfolio via the all in one Ledger Wallet app: buy, sell, send, receive, swap, stake and more across popular blockchains. 15,000+ coins & tokens in a single dashboard. Keep a close eye on the market. Compare service providers. Track performance. Get timely alerts. Build your portfolio with confidence.
- Enjoy Bluetooth connectivity, iOS access, and hours of battery use with this mobile-first, secure backup signer. Freedom you can depend on.
- Genuine Check: confirm your signer is authentic during setup with the Ledger Wallet app.
- Protect your signer: keep it in mint condition at all times with a bespoke Pod or Case to avoid scratches and everyday wear and tear.
Can I sign a Solana transaction offline without using a durable nonce?
Yes. You can build a normal transaction, obtain its recent blockhash, transfer the unsigned message to an offline signer, collect the signature, and return the signed bytes to a connected broadcaster. This is appropriate when every required signer can complete the process before the recent blockhash expires.
The exact message is what each signer authorizes. It includes the fee payer, recent blockhash or nonce, account addresses, account permissions, and instruction order. The broadcaster must transmit those signed bytes without changing them. Editing an instruction, replacing the fee payer, refreshing the blockhash, or changing any account after signing creates a different message and requires signatures again.
How long does an offline-signed Solana transaction remain valid?
For an ordinary transaction, validity is tied to the recent blockhash queue, not to the fact that the signature was produced offline. Solana’s current transaction-pipeline documentation describes a 150-slot processing-age limit. The practical elapsed time in seconds varies with network slot timing, so it should not be treated as a fixed number of minutes.
Free tools Windows power users keep installed
One-click scans. No signup required.
All signers must return their signatures and the completed transaction must be submitted while the blockhash is still acceptable. If the blockhash expires, the signed message cannot be repaired by replacing only that field: changing it changes the message every signer signed. The transaction must be rebuilt with a new blockhash and signed again by every required signer.
Normal offline-signing workflow
- Prepare the message online or in a coordinator. Set the fee payer, instructions, account metas, permissions, and a current recent blockhash.
- Freeze the serialized message. Record the exact bytes or an equivalent verifiable representation for every signer.
- Move only the unsigned message to the offline signer. Use the wallet’s supported transfer method and verify the transaction details on the isolated device.
- Sign without network access. The signer returns a signature over the frozen message.
- Collect all required signatures before expiry. Do not alter the message while waiting for another signer.
- Broadcast the unchanged signed transaction. Monitor confirmation and expiry information from the connected environment.
If the process may exceed the recent-blockhash window, use a durable-nonce design instead of assuming that offline storage makes the ordinary transaction persistent.
What is a Solana durable nonce?
A durable nonce is a value stored in a System Program-owned nonce account. An initialized nonce account records an authority public key, the durable nonce value, and the lamports-per-signature fee rate from the last time the nonce was advanced. The stored value is placed in the transaction’s recent_blockhash field, even though it is not a normal recent blockhash.
Rank #2
- Simply & securely take control of your digital assets and identity with the all-in-one Ledger Wallet crypto app and Ledger Flex touchscreen signer.
- Digital asset control at your fingertips: manage 15,000+ crypto across multiple chains. Earn rewards. Top up & share with ease. Explore DeFi with confidence. Collect and showcase NFTs. Make informed choices with clarity.
- Connect effortlessly with Ledger Wallet: pair your secure Ledger signer with the all in one Ledger Wallet crypto app to manage thousands of digital assets across multiple devices and accounts with Ledger Sync from a single, secure dashboard.
- Cutting-edge design: monitor the market, compare rates, and Clear Sign transactions on the secure, high resolution, 2.8'' E Ink touchscreen.
- This is what security feels like: Ledger touchscreen signers all come with a private, offline, PIN-protected backup, Ledger Recovery Key, to never lose access to your assets.
The transaction must begin with an AdvanceNonceAccount instruction. Validators recognize this first-instruction pattern, verify that the nonce account is initialized, confirm that its stored value matches the transaction’s lifetime value, check that the nonce can advance, and verify that the nonce authority signed. When those checks pass, the nonce advances before the remaining instructions execute.
Durable-nonce signing sequence
- Create and initialize a nonce account. Assign a nonce authority and fund the account as required by the current Solana tooling and account rules. The Solana CLI reference follows Agave v4.2.1 and documents the available nonce-account commands.
- Read the current nonce value. Treat it as shared state. Another authorized process can advance it before your transaction is submitted.
- Build the transaction with
AdvanceNonceAccountfirst. Put the stored nonce in the transaction’srecent_blockhashfield and include the correct nonce authority signer. - Freeze and verify the complete message. Check the fee payer, nonce account, authority, instructions, account permissions, and amounts on every signing device.
- Sign offline. The signer can be disconnected from the network because the transaction already contains the durable lifetime value.
- Submit the unchanged signed bytes later. The transaction remains usable only while the stored nonce still matches and has not been advanced.
Solana’s documentation summarizes the intended use this way: For workflows that may take longer or include offline signers, use a durable nonce.
That guidance does not mean every offline transaction requires a nonce; it describes workflows where the ordinary blockhash window is too short.
Offline signing with a recent blockhash vs. a durable nonce
| Question | Recent blockhash plus offline signing | Durable nonce plus offline signing |
|---|---|---|
| What does offline mean? | The private key signs away from the internet; a connected device or coordinator later transmits the signed transaction. | The same separation applies: an isolated signer authorizes bytes and a connected submitter broadcasts them. |
| What sets 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 consumed, or until the transaction no longer matches the nonce account state. |
| What must be coordinated? | All required signatures must be collected and submitted before the blockhash expires. | The nonce account, nonce authority, and stored value must remain valid and unconsumed while the transaction is pending. |
| What does each signer authorize? | The exact message, including fee payer, instructions, accounts, and recent blockhash. | The exact message, including fee payer, instructions, accounts, and durable nonce. |
| What invalidates saved 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 on 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. |
What happens if a Solana durable nonce transaction fails?
Failure has two materially different paths. If validation fails—for example, the nonce account is not initialized, the stored value does not match, the nonce cannot advance, or the required authority signature is missing—the transaction is rejected before state changes. The nonce is not advanced and fees are not charged.
If nonce validation succeeds and a later instruction fails during execution, the transaction has already committed the nonce advancement. The failed instruction does not get its intended result, but the nonce is consumed and transaction fees are still collected. The old signed transaction cannot simply be retried, because it contains the nonce value that has already advanced.
After a nonce is consumed
- Fetch the nonce account’s current state.
- Determine whether the prior transaction was validated and whether any application instruction executed successfully.
- Build a new transaction using the newly stored nonce value.
- Collect signatures over the new message. Never edit the old signed bytes in place.
- Investigate the original execution failure before retrying, especially if the instruction could fail again or produce a duplicate application effect.
A nonce can also be advanced by another authorized transaction before your saved transaction reaches a validator. In that case, the saved transaction is unusable even if no application instruction from it ran. This is the central coordination cost of durable nonces: they extend the waiting period but do not make a signed transaction independent of shared account state.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsWhy changing a signed transaction breaks every signature
Solana signatures cover the serialized message, not a vague intent such as “send approximately this amount.” The message includes the fee payer, lifetime value, every account address and permission flag, and the ordered instruction list. A partial-signing workflow therefore has to preserve one canonical message from construction through broadcast.
Rank #3
- More than just crypto: confirm your device is authentic with Genuine Check, manage all your logins with Ledger Security Key, detect common scams with Transaction Check and more.
- Industry-defining security: battle-tested by the Donjon's white hat hackers, protected by the Secure Element, and powered by Ledger OS.
- Connect effortlessly with Ledger Wallet: pair your secure Ledger signer with the all in one Ledger Wallet crypto app to manage thousands of digital assets across multiple devices and accounts with Ledger Sync from a single, secure dashboard.
- Playful, user-friendly design: monitor the market, compare rates and Clear Sign all transactions on the secure 2.8'' anti-glare, scratch-resistant touchscreen.
- This is what security feels like: Ledger touchscreen signers all come with a private, offline, PIN-protected backup, Ledger Recovery Key, to never lose access to your assets.
- Changing the recent blockhash or durable nonce requires all signatures again.
- Changing the fee payer changes the message and can change who pays fees.
- Adding, removing, or reordering instructions invalidates existing signatures.
- Changing account writability, signer status, program addresses, amounts, or destination accounts invalidates existing signatures.
- Adding a signature to a transaction is allowed only when the underlying message remains identical.
Use a digest, transaction preview, or the wallet’s built-in message-verification display to compare what was constructed with what the offline device is signing. The reviewed Solana documentation establishes the frozen-message requirement, but it does not certify compatibility for any particular retail hardware-wallet model, firmware version, wallet application, or transaction type. Confirm that exact combination before relying on an air-gapped workflow.
Who benefits from durable nonces?
Individual wallet users
A nonce is usually unnecessary when you can connect the wallet, sign, and submit within the ordinary recent-blockhash window. It adds an account to create and fund, an authority key to protect, and a shared value that can be consumed by another process. Choose it when your security or operational process genuinely needs delayed submission, such as an offline signer that may be unavailable for an extended period or a set of approvers operating on different schedules.
Custodians and multi-party approval teams
Teams coordinating signatures across people, locations, or offline devices should model the nonce as a single-use reservation. Assign clear ownership of the nonce authority, record who may advance it, and define what happens when a transaction is rejected, expires operationally, or is superseded. A pending transaction is not safe to keep indefinitely if another authorized operator can advance the same nonce account.
Production signing systems
Applications that sign at scale should separate transaction construction, policy approval, key operations, and submission. Solana’s Signing in Production documentation discusses production signer models and Keychain backends. The choice between a recent blockhash and a durable nonce belongs in the system’s transaction-lifecycle design, alongside retry behavior, idempotency, authority controls, monitoring, and audit logs.
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 a completed network change and there is no final activation date as of October 2026. The Solana Foundation’s Durable Nonce Deprecation page labels the work In Development. It says current nonce transactions remain valid until a suitable replacement is audited and live on mainnet, with removal expected roughly six months after the replacement is ready. That is a stated migration approach, not a scheduled date.
The Foundation says ordinary wallets and applications are unaffected and that an individual user needs to act only if they personally use durable nonces. If a custodian or service uses them on your behalf, that custodian is responsible for migration. Do not disable ordinary transactions or move funds solely because a future deprecation is being developed.
Rank #4
- All your digital assets in one place. You can manage thousands of crypto including Bitcoin, Ethereum, Solana, Tether and more.
- Connectivity: USB-C cable connection only. No Bluetooth.Compatible with the Ledger Wallet crypto app, both desktop (Windows, macOS, Linux) and mobile (Android only). Not compatible with iOS.
- Protect your digital assets with the industry's best security: keep your private keys offline in your private signer, battle-tested by the Donjon's white hat hackers, CC EAL 6+ certified Secure Element, constantly updated Ledger OS.
- Effortlessly build your crypto portfolio via the all in one Ledger Wallet app: buy, sell, send, receive, swap, stake and more across popular blockchains. 15,000+ coins & tokens in a single dashboard. Keep a close eye on the market. Compare service providers. Track performance. Get timely alerts. Build your portfolio with confidence.
- Choose the colors that match your style: express your personality and your crypto management mood, color code your signers, one for each use (trading, staking, HOLDing...).
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 rather than relying on special validator-runtime handling. Their execution paths use cross-program invocation (CPI) and a signer program-derived address (PDA).
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11The status is still evolving. The page reports an Anza implementation on Devnet, says the implementations and interfaces are developing, and states that audits precede an Anza v1 release. It does not state that Vector has completed an audit. Neither should be described as a finished, audited mainnet replacement.
Implementation differences that matter to developers
| Area | How the Foundation describes the candidates |
|---|---|
| Signed payload | Anza uses a standard v1 message payload. Vector’s signature covers every top-level instruction. |
| Authorities | Anza allows multiple authorities. |
| Signature schemes | Vector supports additional signature schemes listed on the Foundation page; the exact supported set can change as the design develops. |
| Execution model | Both require authorized instructions to execute through CPI using a signer PDA. |
| Application impact | Programs that require top-level instructions or use CPI guards may need changes. |
| Audit and network status | Anza’s audit is described as preceding v1; the page does not state Vector’s audit status. Neither is presented as live, final mainnet infrastructure. |
The Foundation page reports figures attributed to SIMD Discussion #564: durable nonce transactions represented 3.1% of transactions in one June 2026 epoch 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 and rationale concerning spam and fee concentration, not a general measurement of every Solana epoch.
How to choose the right approach
Use ordinary recent-blockhash signing when:
- All signers can complete approval promptly.
- The connected broadcaster can submit within the recent-blockhash processing-age window.
- You want the simplest wallet and application flow.
- You do not need a transaction to wait for an offline device or delayed approval.
Consider a durable nonce when:
- The signing workflow may outlast the recent-blockhash window.
- Private keys must remain offline while a separate coordinator waits for signatures.
- A custody or approval process needs a deliberately stored transaction lifetime value.
- Your software can monitor nonce-account state, handle single-use consumption, and rebuild transactions after advancement.
Before deploying either workflow
- Verify that every signer can display and authorize the exact Solana transaction format you use.
- Define one source of truth for the serialized message and prohibit ad hoc edits after partial signing.
- Record the fee payer, lifetime value, nonce account, nonce authority, instruction set, and required signers.
- Set alerts for blockhash expiry, nonce advancement, rejected validation, and post-validation execution failure.
- Test recovery with a small-value transaction before moving production funds.
- For a nonce design, restrict and audit who can advance the nonce account.
- Track the deprecation status through official Solana Foundation and Solana Documentation updates rather than assuming a calendar date.
Practical answers for wallet users
Does offline signing make a transaction last forever?
No. An ordinary offline-signed transaction expires with its recent blockhash. Only a transaction designed with a durable nonce gets the nonce-based lifetime behavior, and that nonce can still be consumed or advanced before submission.
Can I refresh the blockhash after collecting signatures?
No. Refreshing it changes the signed message. Rebuild the transaction with the new lifetime value and collect every required signature again.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Can I retry a failed durable-nonce transaction?
Not by resubmitting the same bytes. If nonce validation succeeded, the nonce advanced even when a later instruction failed. Fetch the current nonce, diagnose the failure, construct a new message, and sign it again.
Do I need to migrate now?
Only if you use durable nonces directly or operate a system that does. The October 2026 Foundation guidance says normal transactions are unaffected and that custodians handle migration for nonce use hidden behind a custody service.
Where can I verify the protocol details?
Use Solana’s Durable Nonces, Partial Signing, and Transaction Pipeline documentation, plus the Foundation deprecation update. These pages provide the mechanics, validation rules, processing-age description, and current migration status.
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.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →
