RAPIDBLOCKS: EXECUTION PROOFS THAT OUTLIVE THEIR STATE

Summary from the TLDR Crypto newsletter

A new Ethereum research proposal restructures execution proof validation by splitting monolithic pre-state-to-post-state proofs into three components: one validating transaction execution against declared inputs, and two handling Merkle input/output verification. Block headers commit to the specific values a block reads rather than a pre-state root, allowing proofs to remain valid across multiple slots when state changes do not touch the accessed keys. The design separates per-slot block validation from state root verification on an independent schedule, so block consensus advances without waiting for state computation to complete. The proposal remains early-stage: block proofs must complete within 2.5 seconds from finalization, witness data requirements for Merkle-Patricia tries are unresolved, and safety proofs are verified only via bounded model checking on small instances.