diff options
| author | tv <tv@krebsco.de> | 2026-11-16 17:11:25 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-16 18:28:28 +0100 |
| commit | 59864edb025ccf009ef3c7b560f059c2cd2768ed (patch) | |
| tree | 460f3d374eafa6dd98d1f7043fcaefae9ba2947c /docs | |
| parent | 647c25362a059b354bf06b95d566b76dbe6c0fdc (diff) | |
federation: a party that has a node vote by itself votes by hand through it
A party votes from one client, and may have one node vote by itself, but nothing put the
two together: a node following a party's `false` on a proposal, and its operator backing
the same proposal from a client, is a party voting twice, honestly. So such a party
votes by hand only through that node, which keeps the party's one record of its votes
and refuses a vote the record forbids.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/federation.md | 9 |
1 files changed, 6 insertions, 3 deletions
diff --git a/docs/federation.md b/docs/federation.md index f77c3c4..b453393 100644 --- a/docs/federation.md +++ b/docs/federation.md @@ -244,7 +244,8 @@ proposal is on, and the proposal, by their hashes. casts, it keeps the votes that made its party's earlier proposal on that version dead, so that, once a checkpoint left them out, nothing names its party as voting twice. A party votes from one client: two of its clients backing two proposals at once is - voting twice, as two of its nodes each voting by itself is. + voting twice, as two of its nodes each voting by itself is, or a vote by hand beside + the node that votes for it (Votes a node casts by itself). * **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 @@ -474,7 +475,9 @@ doesn't back, so that one dies and its backers are free. It signs with a key the party's version names, which the party keeps on that node, not apart: one stolen there votes, and writes the party's key set and node list, as the party's, until a version names its keys anew (Keys). A party that won't keep one there -votes by hand. +votes by hand. A party that has a node vote by itself votes by hand only through that +node, which keeps the party's one record of its votes and refuses a vote that record +forbids: a party votes from one client, and that node is it. ### Nodes @@ -661,7 +664,7 @@ crafted events. *Sim*: a simulation. *Bench*: measured, not judged. | 63 | A node joining from the root is shown a chain old keys grew, beside the one the others took | It takes neither, and reports; once a checkpoint passed, it joins from a pinned one, where that chain is refused | unit | | 64 | Checkpoint heads before the current checkpoint, or at which it isn't current, or one in another's history | No version: a version event naming it is refused | unit | | 65 | After a checkpoint, a party that backed a second proposal once its first was dead, the nays that freed it withheld by those who cast them | Not named: its client keeps those nays with its `true` | unit | -| 66 | Two clients of one party back two proposals at once | Voting twice: a party votes from one client | — | +| 66 | Two clients of one party back two proposals at once, or its operator votes by hand beside the node that votes for it | Voting twice: a party votes from one client, the node that votes for it where it has one, through which it votes by hand | — | | 67 | A party keeps a proposal alive that nobody else backs, holding back automatic checkpoints | The party a node follows votes it `false`, and its followers with it, until it is dead | sim | | 68 | A checkpoint proposed at heads that leave out what was written since: a key set dropping a stolen key, say | Not backed: clients and nodes back a checkpoint only where what they held for a while is among its heads, in their history, or above them; a node shows what they lack | unit | |
