Replies: 1 comment
-
Just because of this comment I think we should not make this change because I am not sure the implications of that and if new versions fix it then it will go away pretty soon. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
On the
OnPartialValidationCompleted, if the network has activated some BIP9 deployment, we will proceed to disconnect nodes that does not support the feature we need.That means as soon as a blockchain network activates, it will proceed to disconnect those nodes that does not support, e.g. Segwit.
Recent improvement to this code ensures that the nodes will always announce Segwit-capability, but this does not apply to older versions of the software, so they gets disconnected.
Code:
Should we change this logic to be similar to proven headers, where an % of connections that doesn't support PH, will still be kept around?
If anyone is deploying with flags, they should consider dropping the last logic of the code above in the file
ConnectionManager.cs. Just disable the if check and peer.Disconnect.Beta Was this translation helpful? Give feedback.
All reactions