← Latest papers
💻 computer science

Perils of Parallelism: Transaction Fee Mechanisms under Execution Uncertainty

This paper analyzes how execution parallelism and contingency in modern blockchains create inherent trade-offs between user and scheduler incentives, proving an impossibility result for existing fee mechanisms and proposing a new framework that achieves optimal boundaries for fairness and performance in systems like Sui and Monad.

Original authors: Sarisht Wadhwa, Aviv Yaish, Fan Zhang, Kartik Nayak

Published 2026-06-15
📖 5 min read🧠 Deep dive

Original authors: Sarisht Wadhwa, Aviv Yaish, Fan Zhang, Kartik Nayak

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 a busy highway where, instead of cars driving one by one in a single lane, traffic is now allowed to zip along multiple lanes simultaneously. This is parallel execution in modern blockchains: a way to process many transactions at once to make the system faster.

However, this paper argues that while parallel highways are faster, the current "toll booth" systems (fee mechanisms) are broken. They don't know how to charge fairly when drivers might take different routes, or when fake drivers try to game the system.

Here is the breakdown of the paper's findings using simple analogies.

1. The Two Big Problems

The authors identify two main "perils" (dangers) that happen when you try to charge fees for parallel processing.

Peril A: The "Maybe" Driver (Contingent Transactions)

Imagine you are ordering a custom pizza. You tell the kitchen, "I want a pizza with pepperoni, mushrooms, and olives."

  • The Reality: You only actually eat the pepperoni. The kitchen prepared the mushrooms and olives, but you didn't touch them.
  • The Problem: In a parallel blockchain, a transaction (the pizza order) often says, "I might need these 5 objects (ingredients)." But depending on the current state of the world (the price of pepperoni), it might only end up using 1 object.
    • If you charge for what you use: The kitchen (the scheduler) loses money because they prepared ingredients that went to waste.
    • If you charge for what you said you'd use: You (the user) overpay for ingredients you never touched.

The Paper's Big Discovery: You cannot have it both ways. You cannot design a system where the user never overpays AND the kitchen never loses money on unused prep work. It is a mathematical impossibility. You have to choose who bears the risk: the user or the system.

Peril B: The "Fake" Drivers (Shill Attacks)

Now, imagine a toll booth that charges based on how much traffic is on the road.

  • The User's Trick: A driver wants to pay a low toll. They send a bunch of fake, useless cars (shill transactions) onto the road. These fake cars take up space but don't actually go anywhere. The toll booth sees "heavy traffic" and spreads the cost out, so the real driver pays less.
  • The Toll Booth's Trick: The person running the booth wants to make more money. They send their own fake cars onto the road to make it look like the real drivers are causing a massive traffic jam. The toll booth then charges the real drivers a premium for "congestion."

The Paper's Discovery: Current systems are vulnerable to these tricks. If the system charges based on how much "parallel work" is happening, bad actors can manipulate the math by adding fake transactions to lower or raise fees.

2. The Three Ways to Split the Bill

Since you can't eliminate the risk of unused ingredients (Peril A), the paper suggests three ways to split the bill between the User and the System:

  1. The "User-Friendly" Approach: You only pay for the pepperoni you actually ate.
    • Result: The user is happy (no overpaying), but the kitchen (system) loses money on the wasted mushrooms and olives.
  2. The "Scheduler-Friendly" Approach: You pay for the whole pizza you ordered, even if you only ate the pepperoni.
    • Result: The kitchen is happy (guaranteed revenue), but the user might overpay.
  3. The "Even-Steven" Approach: You split the cost of the wasted ingredients 50/50.
    • Result: A compromise where both parties share the risk of the "maybe" ingredients.

3. The Solution: The "Object-Weighted" Toll Booth

To fix the "Fake Driver" problem (Peril B) while handling the "Maybe" problem, the authors propose a new system called OW-TFM (Object-Weighted Transaction Fee Mechanism).

The Analogy:
Instead of charging based on how many cars are on the road right now (which can be faked), imagine a toll system that charges based on how popular a specific lane was yesterday.

  • If a specific object (like a popular pizza topping) was used a lot in the last block, its price goes up slightly for the next block.
  • If it wasn't used, the price stays low.

Why this stops the tricks:

  • For Users: If you try to add fake transactions to lower your fee, you can't. Adding a fake transaction only increases the usage count of an object, which might raise the price for everyone, including you. You can't lower the price by adding more cars.
  • For the System: The system sets prices based on past data, so it doesn't need to guess what will happen in the future.

4. The Bottom Line

The paper concludes that building a fair, fast, and secure parallel blockchain is hard because of a fundamental trade-off:

  • Speed vs. Fairness: You can't perfectly predict which "ingredients" a transaction will use without actually running it first (which takes time and defeats the purpose of parallelism).
  • Security vs. Efficiency: You can't have a system that is perfectly efficient (charging exactly for what is used) and perfectly secure (immune to fake transactions) at the same time.

The authors suggest that blockchain designers (like those building Sui, Solana, or Monad) must explicitly decide who bears the risk of unused resources (User or System) and use a pricing model based on historical object usage to prevent people from gaming the system with fake transactions.

In short: Parallel blockchains are like a busy kitchen. You can't perfectly charge for a meal before you know what the customer actually eats, and you can't stop people from pretending to order food to mess up the bill. The solution is to agree on who pays for the wasted food and to base prices on what people usually order, not what they say they are ordering right now.

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 →