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

Update section headers

This commit is contained in:
Hsiao-Wei Wang 2021-05-26 03:01:38 +08:00
parent 0142978b60
commit a25bc832b9
No known key found for this signature in database
GPG Key ID: 1111A8A81778319E
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
specs/altair/validator.md
View File

@ -30,8 +30,8 @@ This is an accompanying document to [Ethereum 2.0 Altair -- The Beacon Chain](./
- [Packaging into a `SignedBeaconBlock`](#packaging-into-a-signedbeaconblock) - [Packaging into a `SignedBeaconBlock`](#packaging-into-a-signedbeaconblock)
- [Attesting and attestation aggregation](#attesting-and-attestation-aggregation) - [Attesting and attestation aggregation](#attesting-and-attestation-aggregation)
- [Sync committees](#sync-committees) - [Sync committees](#sync-committees)
- [Sync committee signatures](#sync-committee-signatures) - [Sync committee messages](#sync-committee-messages)
- [Prepare sync committee signature](#prepare-sync-committee-signature) - [Prepare sync committee message](#prepare-sync-committee-message)
- [Broadcast sync committee message](#broadcast-sync-committee-message) - [Broadcast sync committee message](#broadcast-sync-committee-message)
- [Sync committee contributions](#sync-committee-contributions) - [Sync committee contributions](#sync-committee-contributions)
- [Aggregation selection](#aggregation-selection) - [Aggregation selection](#aggregation-selection)
@ -261,9 +261,9 @@ Sync committee members employ an aggregation scheme to reduce load on the global
Sync committee members produce individual signatures on subnets (similar to the attestation subnets) via `SyncCommitteeMessage`s which are then collected by aggregators sampled from the sync subcommittees to produce a `SyncCommitteeContribution` which is gossiped to proposers. Sync committee members produce individual signatures on subnets (similar to the attestation subnets) via `SyncCommitteeMessage`s which are then collected by aggregators sampled from the sync subcommittees to produce a `SyncCommitteeContribution` which is gossiped to proposers.
This process occurs each slot. This process occurs each slot.
#### Sync committee signatures #### Sync committee messages
##### Prepare sync committee signature ##### Prepare sync committee message
If a validator is in the current sync committee (i.e. `is_assigned_to_sync_committee()` above returns `True`), then for every `slot` in the current sync committee period, the validator should prepare a `SyncCommitteeMessage` for the previous slot (`slot - 1`) according to the logic in `get_sync_committee_message` as soon as they have determined the head block of `slot - 1`. If a validator is in the current sync committee (i.e. `is_assigned_to_sync_committee()` above returns `True`), then for every `slot` in the current sync committee period, the validator should prepare a `SyncCommitteeMessage` for the previous slot (`slot - 1`) according to the logic in `get_sync_committee_message` as soon as they have determined the head block of `slot - 1`.
@ -374,7 +374,7 @@ For example, if a validator with index `2044` is pseudo-randomly sampled to sync
###### Signature ###### Signature
Set `contribution.signature = aggregate_signature` where `aggregate_signature` is obtained by assembling the appropriate collection of `BLSSignature`s from the set of `sync_committee_messages` and using the `bls.Aggregate()` function to produce an aggregate `BLSSignature`. Set `contribution.signature = aggregate_signature` where `aggregate_signature` is obtained by assembling the appropriate collection of `BLSSignature`s from the set of `sync_committee_messages`s and using the `bls.Aggregate()` function to produce an aggregate `BLSSignature`.
The collection of input signatures should include one signature per validator who had a bit set in the `aggregation_bits` bitfield, with repeated signatures if one validator maps to multiple indices within the subcommittee. The collection of input signatures should include one signature per validator who had a bit set in the `aggregation_bits` bitfield, with repeated signatures if one validator maps to multiple indices within the subcommittee.