From cf1817e2837ff54b5d6b5d6ec020c602c296de9f Mon Sep 17 00:00:00 2001 From: tv Date: Mon, 16 Nov 2026 04:15:07 +0000 Subject: federation: what a replay refused, tried again; a client votes by its own A replay puts changes neither of which saw the other by their clocks. A party's `true` committed again at a history before the nays that freed it, its clock set between, came before those nays in the replay and was refused, though the old epoch took it: a proposal that passed there might not pass in the new one, and a party not finding its vote might vote again. What the new epoch refuses is tried again once the rest is replayed, and a party's client keeps what its party voted and votes by that, never by what a node shows. --- docs/federation.md | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) (limited to 'docs') diff --git a/docs/federation.md b/docs/federation.md index 39237ed..63aab69 100644 --- a/docs/federation.md +++ b/docs/federation.md @@ -248,7 +248,8 @@ is on, and the proposal, by their hashes. No vote there is no vote. * **A vote never changes**, and **counts as cast**: signed with one of the keys its version names for its party, whatever keys the party writes since. So a vote is checked from itself and its version alone, by a client too, after a remake left it - out. Nobody deletes it, and a write at a vote's place is refused. + out. Nobody deletes it, and a write at a vote's place is refused. A party's client + keeps what its party voted, and votes by that, never by what a node shows. * **A proposal passes** once at least two thirds of its version's parties voted `true` (3·yes ≥ 2·parties). It is **dead** once so many voted `false` that the rest can't pass it (3·(parties − no) < 2·parties). A party whose `true` and `false` on one @@ -517,9 +518,11 @@ snapshot is a function of its base. What a federated node asks of a remake: before. Votes and proposals go by the keys their version names, which the snapshot holds, so they count as cast in the new epoch too, whatever key sets of their party are replayed around them. Whether a place is held already goes by version number, then - `seq`. What the new epoch refuses (its key was dropped, its place given to another) - goes to the quarantine of the node that holds it, and its party signs it again if it - still may. + `seq`. What the new epoch refuses is tried again once the rest is replayed, as the + clocks may have put it before what it builds on (a vote committed again at another + history, before the nays that freed its party); what it refuses then (its key was + dropped, its place given to another) goes to the quarantine of the node that holds it, + and its party signs it again if it still may. So a remake decides nothing that counts, but what it can't hold: of two envelopes of one version and `seq` at a place at the base, the snapshot keeps one, and a write after the @@ -675,6 +678,7 @@ What an attacker does, and what happens. *Unit*: the judging, with crafted chang | 74 | Two federations started under one swarm name | None: a federation is named by its first version's hash | unit | | 75 | A version, set, list, path or value larger than the federation allows | Refused; none can be too large for a sync message | unit | | 76 | Two thirds back a proposal that is no version | It can't be written, nor die; the federation is bound to its version. A node shows that it is none, and clients don't back it | unit | +| 77 | A party's vote committed again at a history before the nays that freed it, its clock set between, then a remake | The replay refuses it at first, and takes it once the rest is in | unit | ## Roads not taken -- cgit v1.3.1