Ethereum Foundation and Verity Formally Verify EIP-8282

The Ethereum Foundation and formal verification firm Verity have completed a formal verification of EIP-8282, surfacing discrepancies that Ethereum researchers now need to reconcile. Verity finished the work in September 2026, ahead of the proposal's Last Call deadline of November 1, 2026.

The proposal itself sets up dedicated contracts to manage builder deposits and exits. Verity's output centered on the correctness of the EIP's runtime bytecode — the low-level code that would actually execute on-chain. That distinction matters. Proving properties about documentation is one thing. Proving them about the code that ships is another.

What did Verity actually prove?

Verity proved three guarantees about the EIP-8282 bytecode. Together, 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, not by an ordinary user.

To stress-test those claims, Verity used six bytecode mutations. Mutation work means deliberately altering the code and checking whether the stated properties catch the change. If a mutation slips through, the proof was too weak. Six mutations, three guarantees, one verified execution layer.

What are the discrepancies?

Here the record gets practical. Verity's review flagged issues for Ethereum researchers to resolve. The source material does not enumerate the specific findings, but their existence is the operative fact: a formally verified specification and its runtime bytecode do not yet fully agree, and the gap landed on researchers' desks before the window closed.

That timing gives the verification practical weight. Findings that arrive before Last Call closes can still shape the specification. Verity's September completion beat the November 1 cutoff with two months to spare.

What does this change for Ethereum?

For developers and protocol researchers, the immediate task is clear. The discrepancies need to be reconciled with the specification — whether by changing the code, changing the spec, or clarifying the intended behavior. Three routes, one goal: alignment between what the proposal says and what the bytecode does.

The three guarantees give researchers a firmer base for that work. They now know the paid call and SYSTEM call paths behave as specified in the areas Verity proved. That narrows the search space considerably when hunting for the remaining mismatches.

The bigger picture

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 carries in shaping Ethereum's core code.

This is not an academic exercise. Builder deposits and exits sit in the proposal's operational core, and dedicated contracts managing them will move real value if the EIP ships. Formal proofs that arrive before a Last Call deadline can bend the specification itself, which is precisely the leverage point verification firms have been arguing they deserve. The November 1 deadline has now passed, and the reconciliation work between Verity's findings and the final EIP-8282 specification will indicate whether formal verification becomes a standing checkpoint in Ethereum's core-development process or stays a one-off audit.