-
Notifications
You must be signed in to change notification settings - Fork 5.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
EIP-2364: eth/64: forkid-extended protocol handshake #2365
Comments
Spec update: ethereum/devp2p#132 |
I haven't been following along very closely, so I'm sorry that this is a dumb question! But, I believe this spec is not only implemented but it's already deployed to the network. Why is this still in the I also have the same question for eth/65: #2465 |
There has been no activity on this issue for two months. It will be closed in a week if no further activity occurs. If you would like to move this EIP forward, please respond to any outstanding feedback or add a comment indicating that you have addressed all required feedback and are ready for a review. |
This is a discussion thread for #2364
Abstract
The
forkid
(EIP-2124) was designed to permit two Ethereum nodes to quickly and cheaply decide if they are compatible or not, not only at a genesis/networking level, but also from the perspective of the currently passed network updates (i.e. forks).EIP-2124 only defined how the
forkid
is calculated and validated, but due to the numerous possible applications, it did not itself spec out how theforkid
should be exchanged between peers. This current EIP requests the inclusion of theforkid
as a new field in the Ethereum wire protocol (eth
) handshake (releasing a new version,eth/64
).By cross validating each others' forks already during the handshake, incompatible nodes can disconnect before expensive block exchanges and validations take place (PoW check, EVM execution, state reconstruction). This furher prevents peer slots from being taken up by nodes that are incompatible, but have not yet been detected as such.
The text was updated successfully, but these errors were encountered: