-
Notifications
You must be signed in to change notification settings - Fork 456
Unstable broadhash consensus #3574
Comments
Version
Version
|
This issue can be linked to #3533 |
In here, no need to use Maybe another issue but connectedPeer and triedPeer seems to create duplicate information and triedPeer has outdated information. |
Now the consensus is too good (
Additionally, probably there is still some issue regarding connecting to itself:
|
PR #3634 will fix the too good consensus, @4miners Regarding the comment about the peer connecting to itself. if you are referring to the log below then its because its the expected behavior, when a node tries to connect to itself, it is rejected with this error and drops the connection based on
|
Expected behavior
Broadhash consensus should be stable.
Actual behavior
Broadhash consensus is unstable which leads to missed blocks.
Steps to reproduce
Tested on network with 10 peers, observe logs.
Which version(s) does this affect? (Environment, OS, etc...)
2.0.0-alpha.0
The text was updated successfully, but these errors were encountered: