You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the History network, post-merge headers require a proof that is rooted in the historicalRoots or historicalSummaries accumulator from the Beacon chain state. These are constructed from a set of merkle proofs showing inclusion of an EL header in a beacon block body, the beacon block header, and then up to the historicalRoots/historicalSummaries accumulator as documented in thesetwo PRs. To allow Ultralight to properly verify these headers we need to build out the following bits:
~~history.verifyInclusionProof needs to be modified to verify post-merge header proofs against the correct accumulator `` Replaced verifyInclusionProof with multiple proof verification utilities
In the History network, post-merge headers require a proof that is rooted in the
historicalRoots
orhistoricalSummaries
accumulator from the Beacon chain state. These are constructed from a set of merkle proofs showing inclusion of an EL header in a beacon block body, the beacon block header, and then up to thehistoricalRoots
/historicalSummaries
accumulator as documented in these two PRs. To allow Ultralight to properly verify these headers we need to build out the following bits:history.verifyInclusionProof
needs to be modified to verify post-merge header proofs against the correct accumulator `` ReplacedverifyInclusionProof
with multiple proof verification utilitieshistoricalSummariesBlockHeaderProof
in the history network Generate and verify post capella proofs #616historicalSummaries
data object in gossip and findContent methods in the beacon network Add support forhistoricalSummaries
tobeacon
network #606The text was updated successfully, but these errors were encountered: