EIP-8025#569
Open
frisitano wants to merge 4 commits intoethereum:masterfrom
Open
Conversation
kevaundray
reviewed
Jan 16, 2026
jsign
reviewed
Jan 16, 2026
12 tasks
Restructure the EIP-8025 endpoints to mirror the actual reference
implementation in `eth-act/lighthouse`:
- GET path: drop the `proofs/` segment.
`/eth/v1/beacon/proofs/execution_proofs/{block_id}`
-> `/eth/v1/beacon/execution_proofs/{block_id}`
- POST path: move under `beacon/`, drop the dedicated `Prover` tag.
`/eth/v1/prover/execution_proofs`
-> `/eth/v1/beacon/execution_proofs`
- POST body: validator-signed proofs wrapped in an object, matching
lighthouse's `SubmitExecutionProofsRequest { proofs: Vec<...> }`.
Drop `ProofGenId` and `GeneratedProof` (no longer used at the HTTP
layer; proof-engine integration is internal to the EL via the
Engine API).
- Signed-proof shape: `ProverSignedExecutionProof { prover_pubkey, .. }`
-> `SignedExecutionProof { validator_index, .. }`. Lighthouse signs
proofs with the validator's BLS key and identifies the signer by
validator index, not by a separate prover pubkey.
- `proof_data` max: 300 KiB -> 400 KiB, matching `MaxProofSize` in
lighthouse and the consensus-specs PR ethereum/consensus-specs#5162.
`redocly lint` passes; `swagger-cli bundle` resolves all refs cleanly.
# Conflicts: # beacon-node-oapi.yaml
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
3 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.
Adds the EIP-8025 beacon-node HTTP API: a
GETfor retrieving execution proofs by block id, and aPOSTfor validators to submit signed execution proofs which the node verifies, stores, and gossips.Both endpoints live under
/eth/v1/beacon/execution_proofs. Proofs are signed by validators (identified byvalidator_index) — there is no separate prover-engine HTTP API; the proof-engine integration is internal to the EL via the Engine API.Aligned with the
eth-act/lighthousereference implementation.MAX_PROOF_SIZEis 400 KiB to match the consensus-specs bump in ethereum/consensus-specs#5162.Related CL specs: ethereum/consensus-specs#5055 (refactor, merged), ethereum/consensus-specs#5162 (size bump, open). Original CL PR: ethereum/consensus-specs#4828 (merged).