Repository navigation
runtime: read the nonce account from parent state when rolling back a failed transaction - #310
Merged
smcio merged 1 commit intoOct 18, 2026
Conversation
… failed transaction
smcio
approved these changes
Oct 18, 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
2 participants
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.
A failed durable-nonce transaction during bloc production could leave its nonce unadvanced, while replay advances it. The rollback in
MaybeAdvanceNonceAccountForFailedTxonly read the slot account store, which starts empty on a leader bank, so a nonce account the slot had not written yet was skipped.It now falls back to parent state, as the fee payer already does in
handleFailedTx. Replay always finds the account in its own store, so its behavior does not change.