You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we connect to a peer and exchange Status messages we validate their ForkID, the fork id is derived from the genesis, chain config, and block number and timestamp of the latest block. When we connect to a peer with the purpose of syncing our fork ids will not match, as our peer should be on a further block. Therefore we shouldn't check that our fork ids are the exact same but instead check for compatibility as described in: https://eips.ethereum.org/EIPS/eip-2124
The text was updated successfully, but these errors were encountered:
When we connect to a peer and exchange
Status
messages we validate theirForkID
, the fork id is derived from the genesis, chain config, and block number and timestamp of the latest block. When we connect to a peer with the purpose of syncing our fork ids will not match, as our peer should be on a further block. Therefore we shouldn't check that our fork ids are the exact same but instead check for compatibility as described in: https://eips.ethereum.org/EIPS/eip-2124The text was updated successfully, but these errors were encountered: