From 9c1d33fd1c2cd0a0a90bef1b4984676d04500e12 Mon Sep 17 00:00:00 2001 From: tv Date: Mon, 16 Nov 2026 04:16:24 +0000 Subject: federation: a party that voted twice read from its votes, by a tool A node reported a party that voted twice, judging each copy of its votes by the history it was taken at, so that a vote committed again elsewhere framed nobody; and the next remake left those histories out. The votes alone tell it: a `true` and a `false` on one proposal, or a `true` on two proposals of one version where both passed or neither is dead by all the votes cast, as an honest party backs another only once the first is dead. A tool over the votes the parties' clients keep reports it, later too; a node reports the versions it refused. --- docs/federation.md | 20 +++++++++++--------- 1 file changed, 11 insertions(+), 9 deletions(-) diff --git a/docs/federation.md b/docs/federation.md index 97a2c5f..6f18feb 100644 --- a/docs/federation.md +++ b/docs/federation.md @@ -300,13 +300,14 @@ which a remake leaves out (Remakes). the same policy; the sides are apart, and a node that lagged behind, or joins, may be shown either first. The parties answer by forking, without the party that voted twice, or with its keys named anew (Forks). -* **A party that voted twice shows**: its two votes on one version, both signed with - keys the version names for it. A node reports it (a log, the API), with both votes, - as it reports every version it refused. Anyone can commit a vote again at another - history, so two `true`s are voting twice only where no copy of either was taken at a - history where the other's proposal was dead; two envelopes of one value at one vote's - place are one vote. A client keeps the votes, as they are signed and anyone can check - them after a remake left them out. That proves its keys signed both, not that it +* **A party that voted twice shows** in the votes alone, both signed with keys their + version names for it: its `true` and `false` on one proposal, or its `true` on two + proposals of one version where both passed, or neither is dead by all the votes cast. + Where a vote was committed, and how often, changes none of it, and two envelopes of + one value at one vote's place are one vote; an honest party backs another proposal + only once the first is dead. A tool over the votes the parties' clients keep reports + it, as they are signed and anyone can check them, after a remake left them out too; a + node reports the versions it refused. That proves its keys signed both, not that it meant to: two of its nodes voting each by itself, or a stolen key, look the same. Taking it out is the parties' choice, and a fork. * **A proposal on a version that isn't current lapses**, with the votes on that @@ -617,7 +618,7 @@ What an attacker does, and what happens. *Unit*: the judging, with crafted chang | 13 | `true` and `false` on one proposal at once | Both held; a node that saw only one may write a version. As 12 | unit, every order | | 14 | A vote changed or deleted | Refused | unit | | 15 | A vote cast at a history from before, on a proposal made since | Refused: its proposal isn't written there | unit | -| 16 | A party's vote committed again at another history | One vote; voting twice only where no copy of either was taken where the other's proposal was dead | unit | +| 16 | A party's vote committed again at another history | One vote; voting twice is read from the votes alone, not from where they were committed | unit | | 17 | A party changes keys after voting or proposing, or beside its vote or proposal | It counts as cast, by its version's keys, at a remake too | unit | | 18 | Votes split, honestly or not | Nothing passes; nays make the proposals dead, and another passes | unit | | 19 | The parties beyond two thirds never vote, or vote `false` on everything | Nothing passes; the others fork | sim | @@ -793,7 +794,8 @@ On a federated swarm: a value may have, each within what a sync message carries. A node that doesn't know the policy stops taking changes. Until stage 4, a federated swarm takes no remake. 2. **What counts**, read by the current version and the keys; shown in the API. - Reports of a party that voted twice, and of versions a node refused. + Reports of the versions a node refused; a tool reporting, from the votes, a party + that voted twice. 3. **Nodes**: membership by the node lists and the party a node's own entry names, the party shown in the handshake before that entry exists, a node syncing with members only (a wire change), neighbours by party. -- cgit v1.3.1