83f9745df1
* restore doppelganger check on connectivity loss https://github.com/status-im/nimbus-eth2/pull/4398 introduced a regression in functionality where doppelganger detection would not be rerun during connectivity loss. This PR reintroduces this check and makes some adjustments to the implementation to simplify the code flow for both BN and VC. * track when check was last performed for each validator (to deal with late-added validators) * track when we performed a doppel-detectable activity (attesting) so as to avoid false positives * remove nodeStart special case (this should be treated the same as adding a validator dynamically just after startup) * allow sync committee duties in doppelganger period * don't trigger doppelganger when registering duties * fix crash when expected index response is missing * fix missing slashingSafe propagation |
||
|---|---|---|
| .. | ||
| api.nim | ||
| attestation_service.nim | ||
| block_service.nim | ||
| common.nim | ||
| doppelganger_service.nim | ||
| duties_service.nim | ||
| fallback_service.nim | ||
| fork_service.nim | ||
| sync_committee_service.nim | ||