Docs Fault Lab
Equivocation
A proposer signs two different commitments for one slot. The two signatures are a slashing proof and the cblock is skipped.
A proposer shows different blocks to different co-proposers, to split the validators. Shows Lemma 2.4, accountable equivocation.
The attack in the run
On slot 64, the first of window 4, proposer 3 sends its co-proposers a second commitment with a different hash, signed with the same key as the first.
What the protocol does
Two commitments for one slot, both under proposer 3's signature, are a proof of equivocation: anyone can check both signatures against the proposer's identity, and a correct proposer never signs two. A validator that has seen it cannot consider the slot agreed (Agreement, condition (d)), so it votes skip and the cblock is skip-certified.
The proof names proposer 3 and no one else, and it holds the two signed messages a slashing rule needs.
The evidence
The run ends done with slashing_proof with the two commitment hashes and the two signatures, then skip_certificate for the cblock. The evidence of a recorded run:
[
{
"description": "Two commitments for one slot, both signed by the same proposer: a slashing proof. Agreement fails and the cblock is skipped.",
"hashes": [
"2a34e6e9373b4998b6009951cf45bbd519425463b0e3f9bd5d278094c80a9a02",
"d534e6e9373b4998b6009951cf45bbd519425463b0e3f9bd5d278094c80a9a02"
],
"kind": "slashing_proof",
"observedFragments": null,
"proposer": 3,
"signatures": [
"3Sdviey443aJBnCoC2dgNLXwxvTETHstdN1YxNXaKCaMcSHJigZQ8jxXtcvt6nowqTpx4YDJ2KThgWzNgtUL5WXv",
"2YkDQhvGBf2ha72NLBtXjyJNcZaDtMPnLeGgUzcqTAHiv3BMCRbBHkomS4bGuehYZF6a7QGz8zzt2B7D4mEiD85M"
],
"slot": 64,
"threshold": null,
"txId": null
},
{
"description": "Validators that saw the slashing proof cannot agree on the slot (Agreed (d)), and the cblock is skip-certified.",
"hashes": [],
"kind": "skip_certificate",
"observedFragments": null,
"proposer": null,
"signatures": [],
"slot": 64,
"threshold": null,
"txId": null
}
]Run it
acrux lab run --scenario equivocation --seed demo --out runs/equivocationOr start it on /lab, or with POST /v1/lab/runs and { "scenario": "equivocation" }. Fault Lab runs