-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Custody punishments & period staggering Take 2 #934
Conversation
* dev: (108 commits) Update scripts/phase0/function_puller.py Update sync_protocol.md Update simple-serialize.md implement assertion sanity check suggested in PR fix argument typing for auxilary transition func Update test_generators/ssz/main.py Update test_libs/config_helpers/README.md Update test_generators/ssz/uint_test_cases.py Update test_generators/ssz/main.py Update test_generators/ssz/renderers.py Update test_generators/operations/deposits.py Update test_generators/operations/README.md Update test_generators/operations/README.md Update test_generators/README.md Update specs/test_formats/shuffling/README.md Update specs/test_formats/operations/deposits.md forks coverage description cleanup Update test_generators/README.md Update test_generators/README.md cleanup deposit tests ...
Would it make sense to just merge in the proposal to make the custody key be the RANDAO 2 periods in the future (#880) into this PR? So |
@@ -251,7 +274,7 @@ def verify_custody_key(state: BeaconState, reveal: CustodyKeyReveal) -> bool: | |||
signature=reveal.key, | |||
domain=get_domain( | |||
fork=state.fork, | |||
epoch=reveal.period * EPOCHS_PER_CUSTODY_PERIOD, | |||
epoch=reveal.period * EPOCHS_PER_CUSTODY_PERIOD + reveal.revealer_index % EPOCHS_PER_CUSTODY_PERIOD, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is a mistake (no need to change this line)
# Conflicts: # specs/core/1_custody-game.md
I would suggest closing this in favour of #880, where I made an attempt to merge all the changes suggested here |
This has been incorporated into #880 and thus is no longer relevant. |
This PR implements the following (and supersedes my previous attempt #872):
max_reveal_lateness
is gradually reduced for timely responsesHereby items 6 and 8 from #864 are addressed.