Replace proof RPC sync with recursive BeaconChainProofs - #297
Draft
creese wants to merge 1 commit into
Draft
Conversation
creese
marked this pull request as ready for review
August 4, 2026 18:47
Contributor
Author
|
@frisitano, could you review the proposed recursive proof sync approach? |
frisitano
suggested changes
Aug 4, 2026
frisitano
left a comment
frisitano
left a comment
Contributor
There was a problem hiding this comment.
Left some comments inline
Comment on lines
+75
to
+76
| historical proofs during sync. Once synced, a verifier continues to | ||
| check per-payload execution proofs as blocks arrive. |
Contributor
There was a problem hiding this comment.
We have concluded that there will be only a single ExecutionProof type: the recursive ExecutionProof version. The internals of how that are constructed using a per payload execution proof are opaque to the CL and do not need to be considered in this work.
| context resolution and binding validation, signature verification, | ||
| cryptographic proof verification, gossip reception, retrieval of | ||
| missing proofs through peer-to-peer RPC, and proof state management. | ||
| retain EIP-8025 execution proofs and recursive `BeaconChainProof` |
Contributor
There was a problem hiding this comment.
For now, I would keep a single ExecutionProof type and treat it as an opaque recursive ExecutionProof type that attests to the validity of the full chain prefix from weak-subjectivity to the head.
creese
marked this pull request as draft
August 5, 2026 04:49
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR updates the Grandine optional execution proofs proposal to replace historical proof retrieval over P2P RPC with a recursive proof-based synchronization model.
The design introduces a rolling
BeaconChainProofthat attests to execution validity from a trusted weak-subjectivity checkpoint to the chain head. A node joining from that checkpoint can verify one recursive proof instead of retrieving and validating a separate execution proof for every historical payload, while continuing to verify per-payload proofs for new blocks.Specifically:
BeaconChainProofand its public input to the proposed data model.ProofEngineto verify both per-payload and recursive proofs.