Ethereum Draft Proposes Constant-Time Execution-Layer Synchronization

An Ethereum Foundation researcher named frisitano has proposed a proof system intended to let Ethereum nodes synchronize the execution layer in constant time from a weak-subjectivity checkpoint.

The draft describes recursively linked proofs that confirm execution payloads from a starting beacon-chain block through the latest head. Each new proof would validate the preceding full-payload proof and then extend the verified chain by one block.

The system would tie the proofs to beacon-chain state. Its public inputs would include the starting and latest beacon-block roots, the chain ID and a version for the stateless-input mode. During propagation, only the two beacon-block roots would need to be broadcast.

The design proposes reusing the envelope processor from EIP-7732 for guest programs. The execution engine would perform verification, while successive proofs on the same branch would carry the earlier proofs needed to establish continuity.

That structure would allow a node to begin execution-layer synchronization from a weak-subjectivity checkpoint without replaying the network’s complete execution history. The draft also proposes distributing the proofs through Ethereum’s gossip network.

A minimal request-response protocol could supplement gossip distribution. It would serve proofs from a cache designed to use a bounded amount of memory.