Fluid limit of a distributed ledger model with random delay

This paper analyzes the asymptotic behavior of a distributed ledger model with batch arrivals and random attachment delays by establishing that its key dynamics, such as the number of leaves, converge to a fluid limit described by delayed partial differential equations, which is further validated through stability analysis and simulations.

Jiewei Feng, Christopher King

Published 2026-03-10
📖 5 min read🧠 Deep dive

Here is an explanation of the paper "Fluid limit of a Distributed Ledger Model with Random Delay" using simple language, analogies, and metaphors.

The Big Picture: A Busy Post Office

Imagine a massive, decentralized post office called IOTA (a type of blockchain). In this post office, people don't just drop letters in a box; they have to do a little bit of work before their letter is accepted.

  1. The Letter (The Block): You write a transaction (a letter).
  2. The Work (Proof of Work): Before the post office accepts your letter, you have to solve a puzzle. This takes time.
  3. The Parents: To solve the puzzle, you look at two other letters that are currently waiting to be processed (called Tips) and say, "I'm building on top of those two."
  4. The Queue: Once you finish the puzzle, your letter gets stamped and added to the ledger. But here's the catch: while you were solving the puzzle, other people might have picked your letter as a "parent" for their own letters.

The Problem: The "Tip" Traffic Jam

In this system, a Tip is a letter that has been accepted but hasn't been "picked up" by anyone else yet.

  • Free Tips: Letters sitting on the counter, waiting to be chosen.
  • Pending Tips: Letters that someone has chosen, but the new person hasn't finished their puzzle yet.

The security of the whole system depends on how fast these Tips get picked up. If there are too many Tips sitting around, it takes a long time for your transaction to be confirmed. If there are too few, the system might get clogged.

The big question the authors asked is: How many Tips will be waiting in line at any given time?

The Challenge: Random Delays

In older models, scientists assumed everyone took exactly the same amount of time to solve the puzzle (e.g., exactly 5 minutes). But in the real world, some people are fast, some are slow, and some get interrupted. The puzzle-solving time is random.

Trying to predict the line length when everyone has a different, random speed is like trying to predict traffic on a highway where some cars drive at 20 mph, some at 70, and some stop for coffee. It's a chaotic mess of math.

The Solution: The "Fluid Limit" (The Water Analogy)

The authors developed a new way to look at this chaos. Instead of counting every single person (vertex) in the system, they decided to treat the system like a flowing liquid.

  • The Old Way (Discrete): Counting every single car in traffic. "Car 1 is here, Car 2 is there..." This is hard when there are millions of cars.
  • The New Way (Fluid Limit): Imagine the traffic is a river. You don't count the drops of water; you measure the flow rate and the depth of the river.

By assuming the number of people arriving is huge and the time between them is tiny, the "jagged" randomness smooths out into a predictable wave. The authors created a set of delayed equations (like a recipe) that tells you exactly how deep the "river of Tips" will be at any moment, even with random delays.

Key Findings in Plain English

  1. The River is Predictable: Even though individual people are random, the overall behavior of the system is very stable. If you know the average speed of puzzle-solving and how many people are arriving, you can predict the number of waiting Tips with high accuracy.
  2. Speed Matters: If the average time to solve a puzzle goes down (people get faster), the "river" of waiting Tips gets shallower. The system clears out faster.
  3. The "Type" System: The authors realized that not all waiting Tips are the same. Some are waiting for a fast puzzle-solver to finish; others are waiting for a slow one. They broke the "river" into different layers (types) based on how long they've been waiting. This gives a much clearer picture of the system's health.
  4. Proof is Solid: They didn't just guess; they used heavy math (martingales and probability bounds) to prove that their "fluid" model is mathematically close to the real, chaotic system. They showed that as the system gets bigger, the error between their prediction and reality becomes almost zero.

Why Does This Matter?

Think of this paper as a weather forecast for a digital economy.

  • For Developers: It helps them design better systems. If they know how many "Tips" will be waiting, they can tune the system to prevent bottlenecks.
  • For Security: If the "river" gets too deep (too many Tips), it might take too long for your transaction to be confirmed, making the system vulnerable to attacks. This model helps calculate the "safe zone."
  • For the Future: It moves beyond simple, rigid models to handle the messy, random reality of the real world, making our understanding of decentralized ledgers much more robust.

In summary: The authors took a chaotic, random system of digital transactions and found a smooth, predictable mathematical "flow" underneath it. They proved that even with random delays, we can accurately predict how busy the system will be, ensuring the digital ledger remains secure and efficient.