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
Any Leap node connected to network when it activates Savanna will be hard-forked out. That Leap node will repeatedly request blocks from its peers because it will not be able to process received blocks.
After Savanna is activated (one proper Savanna block received), net_plugin could reject connections from net versions pre proto_savanna. Then the node would not waste time sending blocks to a node that can't process them.
The text was updated successfully, but these errors were encountered:
This should be generalized for future hard fork releases to the case where new protocol features are activated, rejecting p2p connections from nodes without those protocol features.
bhazzard
changed the title
Reject P2P connections from leap after Savanna activated
Reject p2p connections from nodes without support for active protocol features
Sep 5, 2024
Any Leap node connected to network when it activates Savanna will be hard-forked out. That Leap node will repeatedly request blocks from its peers because it will not be able to process received blocks.
After Savanna is activated (one proper Savanna block received),
net_plugin
could reject connections from net versions preproto_savanna
. Then the node would not waste time sending blocks to a node that can't process them.The text was updated successfully, but these errors were encountered: