summaryrefslogtreecommitdiffstats
path: root/docs/guides
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-19 14:09:23 +0000
committertv <tv@krebsco.de>2026-11-19 15:18:44 +0100
commit8347900a553a3c4c9f9d3fc4a539fd31b41b07d3 (patch)
tree5674d614bd4a79cdc624eaf09d607efff878b227 /docs/guides
parentf85298c40c2528ee801c14a10a7db8920b50fdf8 (diff)
vote: a checkpoint after every version that changes more, unless told otherwise
After a close vote, one key voting twice passes a rival version at a history from before the version that followed, the votes cast before counting with its own, any time until a checkpoint above that version: nodes that took the version refuse it, but one lagging behind, or joining from the root, may take it. A node voting by itself proposed a checkpoint after a version only where its operator set `--store-propose-versions`; now it does unless told otherwise (1 unless set; 0 never so). Versions that change more than moving to a checkpoint are rare, so the cost is a checkpoint each. A default set, store-propose-versions no longer asks for store-vote-key, as store-held-for and store-back-after don't.
Diffstat (limited to 'docs/guides')
-rw-r--r--docs/guides/federation/checkpoints.md4
-rw-r--r--docs/guides/federation/voting-by-itself.md12
2 files changed, 8 insertions, 8 deletions
diff --git a/docs/guides/federation/checkpoints.md b/docs/guides/federation/checkpoints.md
index c929d89..61800a1 100644
--- a/docs/guides/federation/checkpoints.md
+++ b/docs/guides/federation/checkpoints.md
@@ -37,8 +37,8 @@ nothing that can still pass is proposed on the current version.
A node voting for its party by itself proposes checkpoints by its operator's rules: once
it holds so many events beyond its checkpoint (`--store-propose-events`), so many
versions changing more than moving to a checkpoint were written since it
-(`--store-propose-versions`, after every such version with 1),
-or so long after its store moved there (`--store-propose-every`), at the heads it holds,
+(`--store-propose-versions`, 1 unless set), or so long after its store moved there
+(`--store-propose-every`), at the heads it holds,
no more than an event may name (64, which it merges first under a revision with merge
events), where no proposal holds it back ([`voting-by-itself.md`](voting-by-itself.md),
[Its rules](voting-by-itself.md#its-rules)); and it backs what it proposes.
diff --git a/docs/guides/federation/voting-by-itself.md b/docs/guides/federation/voting-by-itself.md
index b01bfd3..73e9df8 100644
--- a/docs/guides/federation/voting-by-itself.md
+++ b/docs/guides/federation/voting-by-itself.md
@@ -51,18 +51,18 @@ or `POST /admin/events/vote` with `{"proposal": "8d02…", "yes": true}`.
* **Proposing checkpoints** (`--store-propose-events COUNT`, `--store-propose-versions
COUNT`, `--store-propose-every DURATION`): once it holds so many events beyond its
checkpoint, so many versions changing more than moving to a checkpoint were written
- since it, or so long after its store moved there by its own clock, it proposes a
- version that only moves to a checkpoint, at the
+ since it (1 unless set, 0 never), 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 it holds, no more than an event may name (64, which it merges first under a
revision with merge events), 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
(`--store-held-for`, ten minutes unless set) whose proposer has none older on the
version. It backs what it proposes, so that the nodes following its party back it too.
- With `--store-propose-versions 1`, it proposes one after every version that changes
- more: after a close vote, one key voting twice can pass a rival version at a history
- from before it, any time later, which nodes lagging behind or joining from the root may
- take; a checkpoint above that version ends that.
+ Unless told otherwise, it proposes one after every version that changes more: after a
+ close vote, one key voting twice can pass a rival version at a history from before it,
+ any time later, which nodes lagging behind or joining from the root may take; a
+ checkpoint above that version ends that.
* **`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.