Ethereum Infrastructure Risk
Speculative DoS in Ethereum
Ethereum’s execution model lets actors speculatively do work before they know they will be paid for it. This paper shows how that gap can be weaponized into a denial-of-service vector.
The main contribution is a set of attacks that decouple the computational burden imposed on blockchain actors from the fees those actors can recover. Instead of exploiting contract logic directly, the attacker exploits speculative processing and mempool mechanics in the surrounding infrastructure.
- Three concrete attack paths. The paper introduces three attacks: ConditionalExhaust, MemPurge, and GhostTX, targeting speculative execution, mempool behavior, and PBS reputation.
- Liveness becomes the casualty. In the combined attack scenario, victims can end up producing empty blocks because their resources are exhausted while their mempools are clogged.
- Cheap attacks, expensive consequences. The expected cost of a one-shot combined attack is reported at roughly $376, with costs falling further for validators or in censored environments.
Why this matters
This matters because some of the most painful blockchain incidents never look like a classic contract exploit at first. They show up as degraded liveness, clogged mempools, or weird builder and validator behavior.
- The infrastructure layer matters. Security reviews that stop at the deployed contract miss attack surfaces in transaction propagation and speculative execution.
- Monitoring has to be cross-layer. Operational teams need telemetry and postmortem tooling that can reason across the mempool, execution path, and resulting chain behavior.
- Directly aligned with Clara. This is the kind of incident context Clara is meant to compress quickly for responders.
Incidents do not stop at the contract boundary. Clara is built for high-speed exploit and incident intelligence across the full attack timeline. Visit clarahacks.com or email [email protected].