EIP-8025 -- The Beacon Chain¶
Note: This document is a work-in-progress for researchers and implementers.
Table of contents¶
- Table of contents
- Introduction
- Types
- Constants
- Execution
- Domains
- Containers
- New
PublicInput - New
ExecutionProof - New
SignedExecutionProof - Beacon chain state transition function
- Block processing
- Execution proof
Introduction¶
These are the beacon-chain specifications to add EIP-8025, enabling stateless validation of execution payloads through execution proofs.
Note: This specification is built upon Fulu and imports proof types from proof-engine.md.
Types¶
| Name | SSZ equivalent | Description |
|---|---|---|
ProofType |
uint8 |
The type identifier for the proof |
Constants¶
Execution¶
Note: The execution values are not definitive.
| Name | Value |
|---|---|
MAX_PROOF_SIZE |
307200 (= 300KiB) |
Domains¶
| Name | Value |
|---|---|
DOMAIN_EXECUTION_PROOF |
DomainType('0x0D000000') |
Containers¶
New PublicInput¶
New ExecutionProof¶
New SignedExecutionProof¶
Beacon chain state transition function¶
Block processing¶
Modified process_block¶
Note: process_block is modified in EIP-8025 to pass PROOF_ENGINE to
process_execution_payload.
Execution payload¶
New NewPayloadRequestHeader¶
Modified process_execution_payload¶
Note: process_execution_payload is modified in EIP-8025 to require both
ExecutionEngine and ProofEngine for validation.
Execution proof¶
Note: Proof storage is implementation-dependent, managed by the ProofEngine.