-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Small tx response verification optimisation #6911
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
all of this looks reasonable,
though one bad side-effect of this is that we now request hashes in random order, which can result in more work during pool import because we might need to reorder sequences from the same account that we request out of nonce order, assuming they are announced in order
wdyt @Rjected
random order already happens when the announcement is validated when data is put into hash map to dedup |
if you think this is a problem now (if I remember correct you wished for the |
Replaces
Vec
forHashSet
inRequestTxHashes
. This simplifies the look up of a hash from aPooledTransactions
response inRequestHashes
, which is done in verifying that hashes in the response were actually requested.