Skip to content

EIP-8025 -- Proof Engine

Note: This document is a work-in-progress for researchers and implementers.

Table of contents

Introduction

This document contains the Proof Engine specification. The Proof Engine enables stateless validation of execution payloads through execution proofs.

Types

Name SSZ equivalent Description
ProofGenId Bytes8 Identifier for tracking proof generation

Proof engine

The implementation-dependent ProofEngine protocol encapsulates the proof sub-system logic via:

  • a state object self.proof_state of type ProofState containing stored proofs
  • a verification function self.verify_execution_proof to verify individual proofs
  • a verification function self.verify_new_payload_request_header to verify new payload request headers using stored proofs
  • a generation function self.request_proofs to initiate asynchronous proof generation

The body of these functions are implementation dependent. The Engine API may be used to implement this and similarly defined functions via an external proof engine.

New verify_execution_proof

1
2
3
4
5
6
7
8
9
def verify_execution_proof(
    self: ProofEngine,
    execution_proof: ExecutionProof,
) -> bool:
    """
    Verify an execution proof.
    Return ``True`` if proof is valid.
    """
    ...

New verify_new_payload_request_header

1
2
3
4
5
6
7
8
9
def verify_new_payload_request_header(
    self: ProofEngine,
    new_payload_request_header: NewPayloadRequestHeader,
) -> bool:
    """
    Verify the corresponding new payload request execution is valid.
    Return ``True`` if proof requirements are satisfied.
    """
    ...

New ProofAttributes

1
2
3
@dataclass
class ProofAttributes(object):
    proof_types: List[ProofType]

New request_proofs

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
def request_proofs(
    self: ProofEngine,
    new_payload_request: NewPayloadRequest,
    proof_attributes: ProofAttributes,
) -> ProofGenId:
    """
    Request proof generation for a new payload request with specified proof attributes.
    Returns a ``ProofGenId`` to track the generation request.

    Generated proofs are delivered asynchronously via the beacon API endpoint
    ``POST /eth/v1/prover/execution_proofs``.
    """
    ...