aboutsummaryrefslogtreecommitdiffstats
path: root/docs/guides/federation/voting-by-itself.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-19 01:48:58 +0000
committertv <tv@krebsco.de>2026-11-19 03:19:23 +0100
commitb00371d1260f4379241a9226d576270dd3a68285 (patch)
tree05e4a4f86689112a75cb05fb09904546345937fa /docs/guides/federation/voting-by-itself.md
parent101080b8a62709cd2606dece086f959781bdf38f (diff)
vote: a proposal holds back checkpoints by a third, or new for a while
A node voting by itself proposes no checkpoint beside a proposal that holds it back, as the checkpoint would lapse it, and a follower backs none so. A proposal held one back where someone but its proposer backed it: two parties, or one and a stolen key, kept a junk proposal alive, and no automatic checkpoint came while it lived, ending it taking nays from more than a third each round. And one new, its proposer alone backing it, was lapsed at once by a checkpoint its writes brought about. A proposal that can still pass holds back now where a third of the parties back it, someone but its proposer among them; or where it is new, held for less than a while (`--store-held-for`), and its proposer has none older on the version: so it is heard before a checkpoint lapses it, once a version for each proposer. Row 67 says so, and a test of nine parties checks it.
Diffstat (limited to 'docs/guides/federation/voting-by-itself.md')
-rw-r--r--docs/guides/federation/voting-by-itself.md12
1 files changed, 7 insertions, 5 deletions
diff --git a/docs/guides/federation/voting-by-itself.md b/docs/guides/federation/voting-by-itself.md
index 97f4eff..cfcdcf3 100644
--- a/docs/guides/federation/voting-by-itself.md
+++ b/docs/guides/federation/voting-by-itself.md
@@ -38,8 +38,8 @@ or `POST /admin/events/vote` with `{"proposal": "8d02…", "yes": true}`.
* **Following** (`--store-follow PARTY,…`): it votes `true` on a proposal where a party
it follows voted `true`, never `false`; by default only on a version that only moves to
- a checkpoint, and only where no proposal changing more can still pass that someone but
- its proposer backs, as a checkpoint lapses it. Even so, the parties following one hand
+ a checkpoint, and only where no proposal changing more holds it back (below), as a
+ checkpoint lapses it. Even so, the parties following one hand
it their votes on checkpoints. With `--store-follow-any`, on any version: that hands
those parties the node's `true`. A party followed so by two thirds of the parties, with
its key kept on a node, passes what it backs.
@@ -51,9 +51,11 @@ or `POST /admin/events/vote` with `{"proposal": "8d02…", "yes": true}`.
DURATION`): once it holds so many events beyond its checkpoint, or so long after its
store moved there by its own clock, it proposes a version that only moves to a
checkpoint, at the heads of what it held for a while (`--store-held-for`, ten minutes
- unless set), where nothing that can still pass is proposed on the current version,
- but a proposal it wouldn't back that nobody backs but its proposer. It backs what it
- proposes, so that the nodes following its party back it too.
+ unless set), where no proposal on the current version holds it back: one it would back
+ that can still pass; one that can still pass that a third of the parties back, someone
+ but its proposer among them; or one held for less than a while whose proposer has none
+ older on the version. It backs what it proposes, so that the nodes following its party
+ back it too.
* **`false` beside** (`--store-nay-beside`): where it backs a proposal that can still
pass, it votes `false` on every other version only moving to a checkpoint, so that of
two checkpoints proposed at once the other dies, and its backers are free.