Ethereum Execution Layer Proposal Simplifies Checkpoint Synchronization

A recursive execution proof design has been proposed to reduce block-by-block proof verification when synchronizing Ethereum's (ETH) execution layer from a weak subjectivity checkpoint. The approach connects the validity of post-checkpoint blocks through proofs, lowering synchronization burden. Foresight News reported that frisitano presented an EIP draft on September 9 outlining a structure that recursively proves the validity of all execution payloads from chain head to beacon block.
Each proof validates the prior proof before linking to the next block. Execution payloads contain transaction execution results in Ethereum blocks. The proposed structure connects execution payload proofs with the beacon chain, incorporating public inputs including start point and head beacon block roots, chain ID, and stateless input mode version. Proofs are propagated by broadcasting two block roots.
The beacon chain is the consensus layer of proof-of-stake Ethereum. Nodes must verify both the linkage of blocks in this layer and execution payload validity. A weak subjectivity checkpoint serves as a recent trusted state for nodes joining or offline for extended periods. The draft was designed to include prior proofs before the latest proof within the same epoch, allowing synchronization nodes to validate linked proofs rather than verifying each proof individually from checkpoint to head.
Proofs are shared via gossip networks with a proposed minimal request-response procedure using limited memory cache. Technical documentation identifies this design as a discussion draft, noting that specific implementation details for connecting execution layer and beacon chain require further refinement before actual node deployment can be determined.
Korean Source
This article is an English localization of a Korean-language crypto news report. Original headline: 이더리움 실행 증명 초안, 체크포인트 동기화 단순화 제안