diff options
| author | tv <tv@krebsco.de> | 2026-11-16 17:15:37 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-16 18:29:34 +0100 |
| commit | be7f95c65ad3a19380b7141558e0ef70784c0b1b (patch) | |
| tree | 45da348468ea7538c31011cb69c92c5640b6f45d /docs/federation.md | |
| parent | 72814677f123a0396eb480246e257e27d4ac214b (diff) | |
federation: a client writes its record of votes before it sends one
A party's client votes by what it keeps, never by what a node shows, but nothing said
what one that lost its record does. It can't go by a node: a `true` it sent through one
may be held back there. So it writes its record before it sends a vote, and one that
lost its record casts nothing on the current version.
Diffstat (limited to 'docs/federation.md')
| -rw-r--r-- | docs/federation.md | 14 |
1 files changed, 8 insertions, 6 deletions
diff --git a/docs/federation.md b/docs/federation.md index 5dbc804..2eb01b8 100644 --- a/docs/federation.md +++ b/docs/federation.md @@ -248,12 +248,14 @@ A party **votes** on a proposal by a `vote` event, naming the version the propos * **A vote 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, and nothing takes it back. A party's client keeps what - its party voted, and votes by that, never by what a node shows. With each `true` it - 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, or a vote by hand beside - the node that votes for it (Votes a node casts by itself). + its party voted, and votes by that, never by what a node shows: it writes its record + before it sends a vote, and one that lost its record casts nothing on the current + version, as a `true` it sent through a node may be held back there. With each `true` + it 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, 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 |
