As reported on November 4, 2026, Verity Labs formally verified the frozen bytecode for two EIP-8282 pre-deployment contracts: one for builder-staking entry and one for exit. The proposal introduces a separate staking role for builders alongside ePBS. The contracts are written in sys-asm and run directly as EVM bytecode.
Before proving properties of the bytecode, the team confirmed the implementation to be checked with the Ethereum Foundation and corrected discrepancies between the EIP text and code. It then stated guarantees in English covering admission, queue consumption, queue controls and fees, translated them into Lean propositions, and proved that the frozen bytecode satisfies them. Six bytecode mutations were also used to test whether the guarantees would detect typical defects.
The proof has a defined boundary. It does not cover consensus-layer scheduling, construction of request lists, BLS validation or decisions about activating an upgrade. Verification of these contracts therefore should not be read as verification of the entire proposed system—or as evidence that the proposal had been activated.