-
Notifications
You must be signed in to change notification settings - Fork 446
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
Add support for eth/67 #4561
Add support for eth/67 #4561
Conversation
# Conflicts: # src/Nethermind/Nethermind.Network/ProtocolsManager.cs
# Conflicts: # src/Nethermind/Nethermind.Init/Steps/InitializeNetwork.cs
switch (message.PacketType) | ||
{ | ||
case Eth66MessageCode.GetNodeData: | ||
break; |
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.
So essentially, it will just timeout on their end?
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.
hmm, good point, I will rethink it
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.
What does the spec says?
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.
Spec obligates us to remove message types GetNodeData
and NodeData
from the eth
protocol, is not specifying our exact behaviour:
https://eips.ethereum.org/EIPS/eip-4938#specification
So I think we should do the same as we do when receiving other not supported messages - ignore without respond
!!! DO NOT MERGE IT BEFORE ##4475!!!
PR mentioned above is needed for snap sync healing phase after dropping
GetNodeData
EIP: https://eips.ethereum.org/EIPS/eip-4938
Changes:
snap
protocol is enabledTypes of changes
Testing
Requires testing
In case you checked yes, did you write tests??