Fix eth/67 vs eth/68 peers for NewPooledTransactionHashes #12997
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
yperbasis
requested review from
AlexeyAkhunov,
antonis19,
AskAlexSharov and
racytech
antonis19
reviewed
Dec 4, 2024
antonis19
reviewed
Dec 4, 2024
antonis19
reviewed
Dec 4, 2024
antonis19
approved these changes
Dec 4, 2024
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.
eth/68 and eth/67 are only different w.r.t. to
NewPooledTransactionHashes. Previously the determination ofmsgcodewas sometimes failing because it relied only on one protocol version, namelyss.Protocols[0].Version.