Ethereum’s security still hinges on two different “phone lines” that let its nodes talk—LibP2P for the new consensus layer and devp2p for the old execution layer—yet current testing looks at them one at a time, leaving gaps an attacker could slip through. We will create a single, easy-to-run framework that bombards both layers with millions of shuffled messages, watches for crashes or odd replies, and automatically spits out bug reports plus ready-to-merge fixes. The open-source tool will plug straight into the three most-used clients, cover every known past network flaw, and aim to uncover at least five new high-severity bugs
Blind-spot security risk Current fuzzing targets either Ethereum’s Consensus-Layer LibP2P or Execution-Layer devp2p; cross-stack interactions remain untested, leaving exploitable gaps. Fragmented tooling & duplicated effort Client teams maintain separate harnesses, wasting resources and still missing mixed-layer bugs. Low coverage of complex state sequences Most fuzzers mutate single packets; they rarely explore multi-step peer-lifecycle states where subtle logic flaws hide. Slow vulnerability turnaround Without an automated, unified workflow, crashes are hard to triage and patch, delaying fixes that protect the whole network. High entry barrier for newcomers Security researchers must spin up two different frameworks, discouraging community audit and knowledge sharing.
The open-source tool will plug straight into the three most-used clients, cover every known past network flaw, and aim to uncover at least five new high-severity bugs