Skip to content
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

unify bn/vc doppelganger detection #4398

Merged
merged 5 commits into from
Dec 9, 2022
Merged

Conversation

arnetheduck
Copy link
Member

@arnetheduck arnetheduck commented Dec 7, 2022

  • fix REST liveness endpoint responding even when gossip is not enabled
  • fix VC exit code on doppelganger hit
  • fix activation epoch not being updated correctly on long deposit queues
  • fix activation epoch being set incorrectly when updating validator
  • use monitoring start as reference time for detecting doppelgangers, not add time
  • move most implementation logic to validator_pool, add tests
  • ensure consistent logging between VC and BN
  • add docs

* fix REST liveness endpoint responding even when gossip is not enabled
* fix VC exit code on doppelganger hit
* fix activation epoch not being updated correctly on long deposit
queues
* fix activation epoch being set incorrectly when updating validator
* move most implementation logic to `validator_pool`, add tests
* ensure consistent logging between VC and BN
* add docs
@github-actions
Copy link

github-actions bot commented Dec 7, 2022

Unit Test Results

         9 files  ±    0    1 053 suites  +30   28m 14s ⏱️ + 2m 50s
  3 193 tests +209    3 000 ✔️ +209  193 💤 ±0  0 ±0 
14 567 runs  +648  14 348 ✔️ +648  219 💤 ±0  0 ±0 

Results for commit 2bd5835. ± Comparison against base commit 2932d3b.

♻️ This comment has been updated with latest results.

@arnetheduck arnetheduck merged commit 6e2a024 into unstable Dec 9, 2022
@arnetheduck arnetheduck deleted the doppelganger-fixes branch December 9, 2022 16:05
arnetheduck added a commit that referenced this pull request Feb 13, 2023
#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)
zah pushed a commit that referenced this pull request Feb 20, 2023
* restore doppelganger check on connectivity loss

#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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant