61f60bdf03
## Issue Addressed NA ## Proposed Changes We have observed occasions were under-resourced nodes will receive messages that were valid *at the time*, but later become invalidated due to long waits for a `BeaconProcessor` worker. In this PR, we will check to see if the message was valid *at the time of receipt*. If it was initially valid but invalid now, we just ignore the message without penalizing the peer. ## Additional Info NA |
||
|---|---|---|
| .. | ||
| lib.rs | ||
| manual_slot_clock.rs | ||
| metrics.rs | ||
| system_time_slot_clock.rs | ||