Repository navigation
fix: use the latest blockhash in durable nonce instructions - #443
Merged
Merged
Conversation
Contributor
Author
Aursen
approved these changes
Oct 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
LiteSVM passes the transaction's recent blockhash to
EnvironmentConfig::new. Agave passes the bank's last blockhash (bank.rs). In a nonce transaction, the recent blockhash is the stored nonce. So one nonce can be used many times under one blockhash. Agave rejects the second use withBlockhashNotFound.Summary of Changes
Pass
self.latest_blockhashtoEnvironmentConfig::new.Testing
Extend
test_durable_nonce. A second nonce use under the same blockhash now fails withBlockhashNotFound. Without the fix, it returnsOk.