Governance

Lean verification of EIP-7002: system-call success and FIFO requests

Read full article at source ↗

Based on a feed excerpt; full article content has not been acquired. Source evidence retrieved 26/10/2026, 16:58:26 UTC.

Briefings

A Lean 4 formal proof establishes that EIP-7002's system-call contract always succeeds and respects a FIFO ordering of withdrawal requests. The contract uses at most 210,000 gas per block, and committed submissions match emitted withdrawals exactly. This applies to Prague, Osaka, BPO1, and BPO2 forks since deployment.

Key points

• The system-call contract at 0x00000961Ef480Eb55e80D19ad83579A64c007002 always succeeds regardless of storage state, using at most 210,000 of 30,000,000 gas per block.
• Withdrawal requests leave in exactly the order they arrived, with committed submissions matching emitted withdrawals and remaining queue entries.

Context

This research formalizes EIP-7002's critical system-call behavior using Lean 4, covering Prague, Osaka, BPO1, and BPO2 forks. It connects deployed bytes to Jaune's block processing semantics with exact gas and request-order guarantees.

Limitations

Proofs cover only valid histories under Jaune's configured block processing. Capacity bound of 2^254 submissions applies only after activation, with no hash premises or balance constraints assumed.

Generated by Bittrees-hosted qwen35-2b sha256:aaf42c8b7c3c on 26/10/2026, 18:46:44 UTC. Based on publisher-provided feed evidence; may not cover the full original article. Check the source for details.

View archived briefing on IPFS
bafybeig3kqb2bqunolaag2mnl7xlsyemsazkw2nyekr67r3vkqkmoset3a