Skip to content

fix: rephrase meaning of attestations,signature,beacon_block_root(#16… #16560

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.

Sign up for GitHub

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

Merged
wackerow merged 2 commits into from
Oct 23, 2025
Merged

fix: rephrase meaning of attestations,signature,beacon_block_root(#16… #16560

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f6479ff
fix: rephrase meaning of attestations,signature,beacon_block_root(#16…
baiwfg2 Oct 23, 2025
4ee5446
chore: auto-format whitespace
wackerow Oct 23, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
48 changes: 24 additions & 24 deletions public/content/developers/docs/blocks/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,36 +50,36 @@ There is a lot of information contained within a block. At the highest level a b

The block `body` contains several fields of its own:

| Field | Description |
| :------------------- | :------------------------------------------------- |
| `randao_reveal` | a value used to select the next block proposer |
| `eth1_data` | information about the deposit contract |
| `graffiti` | arbitrary data used to tag blocks |
| `proposer_slashings` | list of validators to be slashed |
| `attester_slashings` | list of attesters to be slashed |
| `attestations` | list of attestations in favor of the current block |
| `deposits` | list of new deposits to the deposit contract |
| `voluntary_exits` | list of validators exiting the network |
| `sync_aggregate` | subset of validators used to serve light clients |
| `execution_payload` | transactions passed from the execution client |
| Field | Description |
| :------------------- | :----------------------------------------------- |
| `randao_reveal` | a value used to select the next block proposer |
| `eth1_data` | information about the deposit contract |
| `graffiti` | arbitrary data used to tag blocks |
| `proposer_slashings` | list of validators to be slashed |
| `attester_slashings` | list of attesters to be slashed |
| `attestations` | list of attestations made against previous slots |
| `deposits` | list of new deposits to the deposit contract |
| `voluntary_exits` | list of validators exiting the network |
| `sync_aggregate` | subset of validators used to serve light clients |
| `execution_payload` | transactions passed from the execution client |

The `attestations` field contains a list of all the attestations in the block. Attestations have their own data type that contains several pieces of data. Each attestation contains:

| Field | Description |
| :----------------- | :---------------------------------------------------------- |
| `aggregation_bits` | a list of which validators participated in this attestation |
| `data` | a container with multiple subfields |
| `signature` | aggregate signature of all attesting validators |
| Field | Description |
| :----------------- | :------------------------------------------------------------- |
| `aggregation_bits` | a list of which validators participated in this attestation |
| `data` | a container with multiple subfields |
| `signature` | aggregate signature of a set of validators against `data` part |

The `data` field in the `attestation` contains the following:

| Field | Description |
| :------------------ | :------------------------------------------------------- |
| `slot` | the slot the attestation relates to |
| `index` | indices for attesting validators |
| `beacon_block_root` | the root hash of the Beacon block containing this object |
| `source` | the last justified checkpoint |
| `target` | the latest epoch boundary block |
| Field | Description |
| :------------------ | :-------------------------------------------------------------- |
| `slot` | the slot the attestation relates to |
| `index` | indices for attesting validators |
| `beacon_block_root` | the root hash of the Beacon block seen as the head of the chain |
| `source` | the last justified checkpoint |
| `target` | the latest epoch boundary block |

Executing the transactions in the `execution_payload` updates the global state. All clients re-execute the transactions in the `execution_payload` to ensure the new state matches that in the new block `state_root` field. This is how clients can tell that a new block is valid and safe to add to their blockchain. The `execution payload` itself is an object with several fields. There is also an `execution_payload_header` that contains important summary information about the execution data. These data structures are organized as follows:

Expand Down