Docs Fault Lab
Crash
A proposer is down from the window's start. The window continues on the two others, with no skip.
One of the window's proposers is offline for the whole window. Shows Theorem 2.1, NewCon correctness.
The attack in the run
Proposer 3 of window 4 sends nothing: no slices, no commitments, no attestations.
What the protocol does
Its co-proposers close every exchange without its commitment and attest it as ⊥. Their attestations agree, P = {1, 2} is a strict majority of the three, so every slot of the window is agreed on the two blocks and executes without delay (Agreement).
Validators cannot tell an offline proposer from a slow one, so each holds its vote for the window's first cblock until the attestation deadline, 570 ms after ParentReady, and then votes for the rest of the window as each cblock executes (The attestation deadline). The window finalizes on two proposers.
Acrux Net runs the same case without a skip; the figures are on Parameters.
The evidence
The run ends done with two_proposers_continue for the window's first slot, agreed on P = {1, 2}. The evidence of a recorded run:
[
{
"description": "Proposer 3 sent nothing for the whole window; both co-proposers attested it as missing, so slot 64 agreed on P = {1,2} and the window continued on two proposers.",
"hashes": [],
"kind": "two_proposers_continue",
"observedFragments": null,
"proposer": 3,
"signatures": [],
"slot": 64,
"threshold": null,
"txId": null
}
]Run it
acrux lab run --scenario crash --seed demo --out runs/crashOr start it on /lab, or with POST /v1/lab/runs and { "scenario": "crash" }. Fault Lab runs