Skip to content
~/sultan
Chapter 2 crest
Chapter 2 · § 2.3 · Recipe

Fairness as Protocol-Level Ordering

The leader cannot see what is inside the transactions.

Problem

What does it mean for a digital monetary system to be fair? Specifically: what does the leader of a consensus protocol get to know, and when?

Solution

The leader cannot see what is inside the transactions.

Fairness means the rules of the system apply identically to every participant regardless of the participant's position in the consensus protocol. The entity that orders transactions does not get an information advantage from doing so.

In StableZK, transactions are encrypted to a threshold of validators on entry to the mempool, and only decrypted after the leader has committed to their ordering in the block. The leader cannot see the contents of transactions before committing to order. Front-running, sandwiching, and selective reordering are not available, by construction.

Discussion

MEV in the existing L1 ecosystem is a structural property of designs that give leaders content visibility before commitment. Cumulative MEV extraction across the major chains is measured in billions of dollars per year. None of it is misconduct in any legal sense. All of it is a tax on participants who don't operate validator infrastructure.

The fix has been known for years. It has not been adopted because it adds latency, complicates the validator set, and breaks tooling assumptions. None of those costs is structural enough to justify shipping a chain that taxes ordinary users to pay sophisticated infrastructure operators.

ℹ Note The current implementation adds approximately 200ms per block in testnet conditions — meaningful but well below what most users would notice for non-HFT use cases. The right number to beat is "billions per year," not "100ms."

See Also

❦ ❦ ❦