For anyone assessing how builder stakes would be handled, the key question is which parts of EIP-8282 have been checked—and which remain outside the proof. In an account published on November 4, 2026, Verity Labs described its formal verification of the proposal’s builder-staking entry and exit predeploy contracts. EIP-8282, alongside ePBS, would introduce a separate staking role for builders; this was verification of a proposal, not a claim that the rules had been activated.
The two contracts are written in sys-asm and run directly as EVM bytecode. Verity Labs said it first confirmed the implementation to be verified with the Ethereum Foundation and corrected discrepancies between the EIP text and code. The team then stated guarantees covering admission, queue consumption, queue controls and fees in English, translated them into Lean propositions, and proved that the frozen bytecode satisfies them. It also used six bytecode mutations to check whether the guarantees would catch typical defects.
The proof has a defined boundary. It does not cover consensus-layer scheduling, construction of request lists, BLS verification or decisions about activating the upgrade. Readers should not treat verification of these predeploys as verification of the entire builder-staking system.


