-
-
Notifications
You must be signed in to change notification settings - Fork 323
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
Apply peer action when there are gossip validation errors #3772
Comments
all errors are the same:
|
all of the errors are correct as the validator is really not in the sync committee at the specified slot. This works as designed since some nodes could catch invalid gossip messages and not spread them to the network, other nodes may not see them. This brings another concern: if a node keeps receiving invalid messages from another node, right now it only decreases gossip score of peer, should we also decrease score at lodestar side, and in the end disconnect the peer? |
Maybe the logic to decide what peers to disconnect should consider gossip score too |
What lighthouse does is to also penalize peer at node side depending on the gossip error https://github.com/sigp/lighthouse/blob/c3a793fd73a3b11b130b82032904d39c952869e4/beacon_node/network/src/beacon_processor/worker/gossip_methods.rs#L1339 for example if a peer sends invalid signature attestations for 5 times, it'll get banned at node (lodestar) side due to |
@twoeths is this still relevant? |
yes it is, will work on this |
Describe the bug
Hetzner-s2 shows a lot of rejected ContributionAndProof gossip messages but other nodes show nothing
![Screen Shot 2022-02-18 at 14 28 24](https://user-images.githubusercontent.com/10568965/154637503-c71e76ce-c047-4352-a363-89897771f37b.png)
The
lodestar_gossip_validation_accept_total
metric is the same for all nodes.Expected behavior
The text was updated successfully, but these errors were encountered: