Why Multi-Client Differential Auditing Beats Single-Repo Code Review
Ethereum's upcoming Fusaka upgrade (combining the Osaka Execution Layer hardfork and Fulu Consensus Layer hardfork) introduces EIP-7594 (PeerDAS) , EIP-7825 (Transaction Gas Limit Cap = 16,777,216) , EIP-7883 (ModExp Gas Increase) , and EIP-7934 (RLP Execution Block Size Limit) .
When you read a single client in isolation, subtle deviations from the specification look intentional. When you compare all 7 Execution Layer clients ( go-ethereum , reth , nethermind , besu , erigon , ethereumjs , ethrex ) and all 7 Consensus Layer clients ( lighthouse , prysm , teku , lodestar , nimbus-eth2 , grandine , ethlambda ) side by side against the official specification, discrepancies jump out immediately.
Case Study 1: engine_getBlobsV2 Pre-Osaka Error Code & Syncing Checks
According to execution-apis/src/engine/osaka.md#engine_getblobsv2 :
Clients MUST return -38005: Unsupported fork if the head block timestamp has not reached Osaka.
Clients MUST…