NETSoon

Docs Fault Lab

Private front-run

A proposer tries to read a 2-of-3 transaction and front-run it. Its one fragment is unreadable; the transaction executes after commitment.

A proposer that receives a transaction reads it before its block is sealed and puts its own trade in front. Shows Section 3.2, threshold transactions, and Lemma 2.3.

The attack in the run

A few slots before window 4 the lab seals a transfer 2-of-3 for slot 66 and sends one fragment to each proposer of the window. Receiver 1 is the attacker: it tries to rebuild the transaction from the fragment it holds.

What the protocol does

A fragment holds one Reed-Solomon shard of the ciphertext and one Shamir share of the key (Wire formats). With t = 2, one fragment rebuilds neither: receiver 1 holds 1 of the 2 it would need, so the transaction is unreadable to it while it builds its block.

The three proposers include their fragments without reading them and seal their blocks. Validators decrypt the agreed blocks, find two or more fragments, rebuild the transaction and execute it in its slot (Decoding). By then every block of the slot is fixed, so no proposer can place a trade in front of it.

The evidence

The run ends done with unreadable_fragment with the transaction ID, the fragments the attacker held and the threshold. The evidence of a recorded run:

outcome.json evidence
[
  {
    "description": "Receiver 1 holds 1 of the 2 fragments it would need: neither the ciphertext nor the key can be rebuilt, so it cannot read the transaction before the slot commits.",
    "hashes": [],
    "kind": "unreadable_fragment",
    "observedFragments": 1,
    "proposer": 1,
    "signatures": [],
    "slot": 66,
    "threshold": 2,
    "txId": "9f6766c30a87fcfae0c2dc08acd85b8c2beb60e1e5b72f7fec35e018f8aef5b5"
  }
]

Run it

Terminal
acrux lab run --scenario private-front-run --seed demo --out runs/private-front-run

Or start it on /lab, or with POST /v1/lab/runs and { "scenario": "private-front-run" }. Fault Lab runs