Handle ENR eth2
twoeths opened this issue · comments
This is a continuation of ChainSafe/lodestar#750. This is from spec v0.11:
+ Clients SHOULD connect to peers with fork_digest, next_fork_version, and next_fork_epoch that match local values.
+ Clients MAY connect to peers with the same fork_digest but a different next_fork_version/next_fork_epoch. Unless ENRForkID is manually updated to matching prior to the earlier next_fork_epoch of the two clients, these connecting clients will be unable to successfully interact starting at the earlier next_fork_epoch