Share
The Ethereum Foundation worked with Verity, a formal verification firm, to mathematically check EIP-8282. The proposal governs how block builders enter and leave the system.
The work produced three proven guarantees about the proposal’s runtime bytecode. It also turned up discrepancies that researchers now need to address.
What Verity actually checked
EIP-8282 was created on May 22, 2026. It covers the lifecycle functions of block builders, the parties responsible for assembling blocks on the network.
The proposal sets up dedicated contracts to manage builder deposits and exits.
Verity finished its verification work in September 2026. The firm’s output centered on the correctness of the EIP’s runtime bytecode, which is the low-level code that would actually execute onchain.
Verity proved three guarantees. They confirm the bytecode correctly handles the scenarios tied to user submissions, meaning paid calls, as well as SYSTEM calls. SYSTEM calls are invocations made by the protocol itself rather than by an ordinary user.
The crypto and markets news you actually need—every morning.
Daily. Free. Join 34,000+ readers across crypto, finance, and policy.
We respect your privacy. Unsubscribe anytime.
Proofs, mutations and the discrepancies
Verity used six bytecode mutations to confirm its properties. Mutation work of this kind generally means deliberately altering the code to see whether the stated properties catch the change.
Then came the discrepancies. Verity’s review flagged issues for Ethereum researchers to resolve.
Where EIP-8282 sits in the process
The Last Call deadline for EIP-8282 was November 1, 2026. Verity’s work wrapped up in September, ahead of that cutoff.
That timing gives the verification practical weight. Findings that arrive before Last Call closes can still shape the specification.
What this means for Ethereum
For developers and protocol researchers, the immediate task is clear. The discrepancies Verity surfaced need to be reconciled with the specification, whether by changing the code, changing the spec, or clarifying the intended behavior.
The three guarantees give researchers a firmer base for that work. They know the paid call and SYSTEM call paths behave as specified in the areas Verity proved.
What to watch next is how researchers respond to Verity’s findings. The resolution of those discrepancies, and whether the final specification changes as a result, will show how much influence formal verification now has in shaping Ethereum’s core code.
