aboutsummaryrefslogtreecommitdiffstats
path: root/docs/guides/federation/voting-by-itself.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/guides/federation/voting-by-itself.md')
-rw-r--r--docs/guides/federation/voting-by-itself.md12
1 files changed, 6 insertions, 6 deletions
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.