From d17350c0fab17f6d2930a5998f33122b0b9fb7bf Mon Sep 17 00:00:00 2001 From: Pawan Dhananjay Date: Mon, 16 Aug 2021 23:30:18 +0000 Subject: [PATCH] Lower penalty for past/future slot errors (#2510) ## Issue Addressed N/A ## Proposed Changes Reduce the penalties with past/future slot errors for sync committee messages. --- .../network/src/beacon_processor/worker/gossip_methods.rs | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/beacon_node/network/src/beacon_processor/worker/gossip_methods.rs b/beacon_node/network/src/beacon_processor/worker/gossip_methods.rs index 4c71e3ca0..68deb9248 100644 --- a/beacon_node/network/src/beacon_processor/worker/gossip_methods.rs +++ b/beacon_node/network/src/beacon_processor/worker/gossip_methods.rs @@ -1232,9 +1232,9 @@ impl Worker { "type" => ?message_type, ); - // Peers that are slow or not to spec can spam us with these messages draining our - // bandwidth. We therefore penalize these peers when they do this. - self.gossip_penalize_peer(peer_id, PeerAction::LowToleranceError); + // Unlike attestations, we have a zero slot buffer in case of sync committee messages, + // so we don't penalize heavily. + self.gossip_penalize_peer(peer_id, PeerAction::HighToleranceError); // Do not propagate these messages. self.propagate_validation_result(message_id, peer_id, MessageAcceptance::Ignore);