← Latest papers
💻 computer science

Position Paper: Denial-of-Service Against Multi-Round Transaction Simulation

This paper introduces evasive, low-cost denial-of-service attacks that exploit multi-round transaction simulation and inter-transaction dependencies to disrupt Ethereum bundling services like Flashbots, significantly reducing builder revenue and slowing block production, while also proposing mitigation strategies.

Original authors: Yuzhe Tang, Yibo Wang, Wanning Ding, Jiaqi Chen, Taesoo Kim

Published 2026-04-24
📖 4 min read☕ Coffee break read

Original authors: Yuzhe Tang, Yibo Wang, Wanning Ding, Jiaqi Chen, Taesoo Kim

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine the Ethereum blockchain as a massive, high-stakes auction house where people are constantly trying to buy and sell digital items.

In this auction house, there are special workers called Block Builders. Their job is to gather all the pending bids (transactions) from the crowd, organize them into a neat package (a block), and hand that package to the auctioneer (the validator) to be officially recorded.

To make the most money, these builders use a clever system called Flashbots Bundles. Instead of just grabbing bids randomly, they run a multi-round rehearsal.

  • Round 1: They try out a few different orders of bids to see which one makes the most profit.
  • Round 2: They tweak the order again.
  • Round 3: They try again.
  • Final Round: Once they find the perfect order, they lock it in and send it to the auctioneer.

During these rehearsal rounds, the builders are essentially "pretending" to execute the transactions to see what happens. If a bid fails in the rehearsal, they throw it out before the final show.

The Problem: The "Ghost" Attack

The researchers in this paper discovered a way to hack this rehearsal system. They found a way to make the builders waste all their time and energy during the final, real round, without the builders even realizing they were being attacked until it was too late.

Here is how they did it, using a simple analogy:

The Analogy: The "Trap Door" in a Play

Imagine the Block Builder is a stage director rehearsing a play with a cast of actors (the transactions).

  1. The Old Way (Previous Attacks):
    Before this paper, hackers tried to break the play by having an actor scream loudly or run around wildly during the rehearsal.

    • Why it failed: The director (the builder) is smart. If an actor screams during the rehearsal, the director just says, "Okay, that's a bad take," and throws that actor out of the rehearsal. The play continues smoothly, and the hacker gets kicked out.
  2. The New Way (This Paper's Attack):
    The researchers invented a "Trojan Horse" strategy. They created a sequence of actors (transactions) that work together like a Rube Goldberg machine.

    • Actors 1 to N-1: These actors enter the stage and do nothing but set up a hidden trap. They whisper to each other, "Okay, the stage is ready." The director watches them, sees they are behaving perfectly, and lets them stay.
    • The Trap: These actors have set up a secret condition. They are waiting for a specific signal that only happens in the Final Round.
    • The Final Actor: When the director finally says, "Okay, this is the real show, let's go!" (the final round), the secret signal is triggered. Suddenly, the first N-1 actors all start screaming, running, and causing chaos at the exact same time.

Why This is Dangerous

  • Evasive: Because the actors behaved perfectly during the rehearsals (Rounds 1 through N-1), the director never kicked them out. They were allowed into the final, real show.
  • Inter-Dependent: The chaos only happens because the actors were talking to each other and sharing a secret state. Previous hackers tried to use "lone wolf" actors who acted alone, which didn't work. These new hackers used a "team" approach.
  • The Result: The director is now stuck dealing with a massive, chaotic mess in the middle of the real show. The show slows down to a crawl, the director loses money, and the other actors (normal users) can't get their lines in.

The Takeaway

The paper shows that by using a team of coordinated transactions that hide their malicious intent until the very last moment, attackers can crash the system that builds blocks.

  • Cost: It's very cheap for the attacker to set up.
  • Risk: It's "risk-free" because the attackers don't lose any money if the attack fails; they just look like normal users until the trap springs.
  • Impact: It slows down the entire blockchain ecosystem and hurts the people running the auction house.

The authors conclude that while we can try to build better "security guards" (mitigations) to catch these teams, the fundamental design of running multiple rehearsal rounds makes it very hard to stop this specific type of trick. It's a new kind of vulnerability that no one had seen before because everyone was looking for lone wolves, not coordinated teams.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →