Skip to content

Commit

Permalink
Adjust options for getting historical_summaries based on feedback
Browse files Browse the repository at this point in the history
  • Loading branch information
kdeme committed Oct 21, 2024
1 parent adf6db5 commit ec0200c
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion history/history-network.md
Original file line number Diff line number Diff line change
Expand Up @@ -439,7 +439,7 @@ Additionally the SSZ container holds a `BeaconBlock` hash_tree_root and a slot.
This chain of two proofs allows for verifying that an EL `BlockHeader` is part of the canonical chain. The only requirement is having access to the beacon chain `historical_summaries`.
The `historical_summaries` is a [`BeaconState` field](https://github.com/ethereum/consensus-specs/blob/dev/specs/capella/beacon-chain.md#beaconstate) that was introduced since the Capella fork. It gets updated every period (8192 slots). The `BlockProofHistoricalSummaries` MUST be used to verify blocks from the Capella fork onwards.

The Portal beacon network [provides access](./beacon-chain/beacon-network.md#historicalsummaries) to an up to date `historical_summaries` object.
The `historical_summaries` can be taken from the CL `BeaconState` (e.g. via [Beacon API](https://ethereum.github.io/beacon-APIs/#/Debug/getStateV2)) or the Portal beacon network can be used to [provide access](./beacon-chain/beacon-network.md#historicalsummaries) to an up to date `historical_summaries` object."

The relationship of the beacon chain structures that are used for the `BlockProofHistoricalSummaries` can be seen below:

Expand Down

0 comments on commit ec0200c

Please sign in to comment.