This repository has been archived by the owner on Nov 6, 2020. It is now read-only.
Fixing last nonce values in case transaction is replaced #1359
Conversation
This file contains 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
| self.move_matching_future_to_current(sender, current_nonce, current_nonce); | ||
| // This will keep consistency in queue | ||
| // Moves all to future and then promotes a batch from current: | ||
| self.remove_all(sender, current_nonce); |
There was a problem hiding this comment.
The logic in remove_all is the same - no changes here.
gavofyork
added
A8-looksgood 🦄
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
When there was couple of transactions pending, and one of them (not the one with highest nonce) is replaced with new transaction with higher gas price the
last_noncewas returning incorrect value.