Governance
How large can EIP-8141's validation budget be? A mempool DoS benchmark
Publication: Ethereum Research - Latest topics
Author: deanstef
Source published: 06/11/2026, 23:26:40 UTC
Briefing created: 07/11/2026, 00:41:22 UTC
Based on a feed excerpt; full article content has not been acquired. Source evidence retrieved 06/11/2026, 23:28:26 UTC.
Briefings
A research paper by Stefano De Angelis, Daniil Ankushin, and Manuel Arto from Nethermind investigates whether EIP-8141's validation budget can be increased to support privacy and post-quantum signatures. The study tests a denial-of-service attack where an attacker floods a node with transactions that burn significant CPU but fail validation, potentially slowing block processing. The authors found that without in-client protections, block processing delays increase by up to 25 ms at 15M gas/s, risking missed attestation deadlines. With protections, a 300k gas cap remains viable at 100 tx/s, admitting only 12% of honest transactions under a flood. The paper concludes that raising the budget requires in-client safeguards to prevent DoS attacks.
Key points
- The paper tests a denial-of-service attack where an attacker floods a node with transactions that burn significant CPU but fail validation, potentially slowing block processing.
- Without in-client protections, block processing delays increase by up to 25 ms at 15M gas/s, risking missed attestation deadlines on the slowest machine.
Context
This research addresses the critical question of whether EIP-8141's validation budget can be increased to support privacy and post-quantum signatures, which currently require higher gas costs than the current 100k limit. The study evaluates the impact of raising the cap on node performance and security, specifically testing a denial-of-service attack scenario where an attacker floods the node with transactions that burn significant CPU but fail validation.
Limitations
The study was conducted on a single Nethermind node with limited hardware coverage, primarily focusing on local builder profiles and the slowest machine. Results may not generalize to all node configurations or network conditions. The research is presented as a post and includes uncertainty regarding the exact impact of different hardware tiers and network conditions on block processing delays.
Generated by Bittrees-hosted qwen35-2b sha256:aaf42c8b7c3c on 07/11/2026, 00:41:22 UTC. Based on publisher-provided feed evidence; may not cover the full original article. Check the source for details.
View archived briefing on IPFS
bafybeif3tcx6gp5t623th74ywuqeoqopdjkahkmo2kr3ayuws7zlbge7jm