fix p2p incompatible forks for opbnb testnet and mainnet #17
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
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.
opbnb introduced the Fermat hardfork during the hardfork setup. Unlike traditional hardforks, Fermat hardfork does not have Block or Time suffixes. While op-geth ignores this hardfork in its forkid calculation, reth includes it, causing mismatched forkids and connectivity issues during P2P connections.
To address this, a temporary solution has been implemented to adjust reth's forkid calculation logic by excluding the Fermat hardfork from the computation.