SnifferCoin

Wallet custody, cryptographic trust boundaries, vulnerabilities, audits and practical defensive habits

What EIP-8282’s Builder-Staking Verification Does—and Does Not—Prove

For anyone assessing a custody or security claim, the key question is what was actually verified. In a report published on November 4, 2026, Verity Labs described a formal verification of the builder-staking entry and exit predeploy contracts in the proposed Ethereum EIP-8282. The work does not establish that the proposal has been activated or that every part of its surrounding system is secure.

EIP-8282, alongside ePBS, would introduce a separate staking role for builders. Its two predeploy 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 addressed discrepancies between the EIP text and code. The team then stated guarantees in English covering admission, queue consumption, queue control and fees, translated them into Lean propositions, and proved that the frozen bytecode satisfies them.

The team also tested six bytecode mutations to check whether the guarantees would detect representative defects. That is a check on the verification approach, not a claim that every possible defect has been ruled out.

The proof boundary matters: the work does not cover consensus-layer scheduling, construction of request lists, BLS validation, or decisions about activating the upgrade. Readers evaluating the proposal should keep those unverified components separate from the guarantees proved for the two contracts.