From e5f8df2a78f26d5928d1c96573dae5620dba5e25 Mon Sep 17 00:00:00 2001 From: tv Date: Thu, 19 Nov 2026 01:48:58 +0000 Subject: docs: quiet parties, proof of voting twice, the next change keeping the number From the red-team review of the design: * a party that never votes holds those backing a proposal short by as many votes: they can neither pass it nor back another, a compromise all others would pass among them; `federation.md` draws that out, and the promises guide says so; * a client keeps its own votes and the nays that freed it, not another party's two: where keys voted twice, whoever saw it keeps the votes naming the party before a checkpoint leaves them out; * nothing but agreement keeps a party from using a change that keeps the federation's number before every node runs it: the next such change names itself in the version, so that two thirds decide when, and a node not running it stops at that version. --- docs/guides/federation/when-things-go-wrong.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'docs/guides/federation/when-things-go-wrong.md') diff --git a/docs/guides/federation/when-things-go-wrong.md b/docs/guides/federation/when-things-go-wrong.md index 7c814c2..fad11c5 100644 --- a/docs/guides/federation/when-things-go-wrong.md +++ b/docs/guides/federation/when-things-go-wrong.md @@ -38,7 +38,9 @@ continuum-party twice tv.record lass.record makefu.record That proves the party's keys signed both, not that it meant to: two of its clients, two of its nodes each voting by itself, a vote by hand beside a node voting for it, or a -stolen key look the same. Keep the records: once a checkpoint left those votes out, they +stolen key look the same. Keep the records, and the two votes naming the party, fetched +from a node while it holds them (`GET /events/{id}`): a client keeps its own votes and the +nays that freed it, not another party's, and once a checkpoint left those votes out, they show nowhere else. ## Choosing a side -- cgit v1.3.1