-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gossamer should not ban other gossamer nodes #2098
Comments
Was unable to reproduce this issue on current development branch. Block production fails after the epoch transition. The actual epoch varies from run to run. Will pick this back up after @noot finishes her refactor of BABE. |
Was able to replicate this in one of my branches. I saw some 3009 negative reputation changes, out of which 2851 were because of duplicate gossip messages. |
Some common negative peer reward
frequency 33
frequency 3009
frequency 6 The message of banned threshold is coming right after negative rewards by unsupported protocol, which makes sense. bunch such negative reward could easily get the peer below banned threshold. |
So, I am seeing that sometime we fail to check if |
I can replicate this on development as well with a 4 node network. |
Task summary
peerset
reportPeer
function to check if a peer reaches theBannedThresholdValue
, you will see that this ends up happening quite often.The text was updated successfully, but these errors were encountered: