status-im/eth2.0-specs
2
0
Fork 0
mirror of https://github.com/status-im/eth2.0-specs.git synced 2025-01-20 15:38:55 +00:00
Code Issues Projects Releases Wiki Activity

Typo in validator.md

Browse Source
This commit is contained in:
Potuz 2024-08-02 12:50:25 -03:00
parent b082140312
commit 74124f521b
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
specs/_features/eip7732/validator.md
View File

@ -12,7 +12,7 @@ This document represents the changes and additions to the Honest validator guide
- [Attestation](#attestation)
- [Sync Committee participations](#sync-committee-participations)
- [Block proposal](#block-proposal)
- [Constructing the new `signed_execution_payload_header_envelope` field in `BeaconBlockBody`](#constructing-the-new-signed_execution_payload_header_envelope-field-in--beaconblockbody)
- [Constructing the new `signed_execution_payload_header` field in `BeaconBlockBody`](#constructing-the-new-signed_execution_payload_header-field-in--beaconblockbody)
- [Constructing the new `payload_attestations` field in `BeaconBlockBody`](#constructing-the-new-payload_attestations-field-in--beaconblockbody)
- [Blob sidecars](#blob-sidecars)
- [Payload timeliness attestation](#payload-timeliness-attestation)
@ -71,7 +71,7 @@ Sync committee duties are not changed for validators, however the submission dea
Validators are still expected to propose `SignedBeaconBlock` at the beginning of any slot during which `is_proposer(state, validator_index)` returns `true`. The mechanism to prepare this beacon block and related sidecars differs from previous forks as follows
#### Constructing the new `signed_execution_payload_header_envelope` field in `BeaconBlockBody`
#### Constructing the new `signed_execution_payload_header` field in `BeaconBlockBody`
To obtain `signed_execution_payload_header`, a block proposer building a block on top of a `state` must take the following actions:
* Listen to the `execution_payload_header` gossip global topic and save an accepted `signed_execution_payload_header` from a builder. Proposer MAY obtain these signed messages by other off-protocol means.