status-im
/
eth2.0-specs
mirror of https://github.com/status-im/eth2.0-specs.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Remove attesting during opt sync

This commit is contained in:
Paul Hauner 2021-12-13 19:03:35 +11:00
parent 8918823071
commit 7f5b7d1535
No known key found for this signature in database
GPG Key ID: 5E2CFF9B75FA63DF
1 changed files with 1 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
sync/optimistic.md
View File

@ -130,20 +130,7 @@ If the latest valid ancestor is `None`, the validator MUST NOT produce a block.
An optimistic validator MUST NOT participate in attestation (i.e., sign across the An optimistic validator MUST NOT participate in attestation (i.e., sign across the
`DOMAIN_BEACON_ATTESTER`, `DOMAIN_SELECTION_PROOF` or `DOMAIN_BEACON_ATTESTER`, `DOMAIN_SELECTION_PROOF` or
`DOMAIN_AGGREGATE_AND_PROOF` domains), unless one of the follow exceptions are `DOMAIN_AGGREGATE_AND_PROOF` domains).
met:
#### Exception 1.
If the justified block is fully verified (i.e., `not
is_optimistic(justified_block)`, the validator MAY sign across the following
domains:
- `DOMAIN_BEACON_ATTESTER`: where `attestation.data.beacon_block_root == hash_tree_root(recent_valid_ancestor(head))`.
- `DOMAIN_AGGREGATE_AND_PROOF` and `DOMAIN_SELECTION_PROOF`: where `aggregate.message.aggregate.data.beacon_block_root == hash_tree_root(recent_valid_ancestor(head))`
If the recent valid ancestor is `None`, the validator MUST NOT participate in
attestation.
### Participating in Sync Committees ### Participating in Sync Committees