aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-19 14:09:05 +0000
committertv <tv@krebsco.de>2026-11-19 15:18:42 +0100
commitf85298c40c2528ee801c14a10a7db8920b50fdf8 (patch)
tree1eef6e26be145d819b5280142f9a6aa277ec4b3f /docs
parent59d8d6f9c4f539ac9392872026d99a93f66102ee (diff)
vote: the version that moved the store counts not toward the next checkpoint
`--store-propose-versions` counted the versions since the checkpoint's version, the one current at its heads. The version that moved the store there is written after its heads, so it counted: with 1, a node proposed a checkpoint again as soon as it backed one (`--store-back-after` after the move), and the next one, and so on, every ten minutes for good. It counts the versions written since that change more than moving to a checkpoint now (`State::changed_since_checkpoint`): with 1, one checkpoint after every other version, and none after a checkpoint. The test goes on past the move.
Diffstat (limited to 'docs')
-rw-r--r--docs/example.toml6
-rw-r--r--docs/guides/federation/checkpoints.md3
-rw-r--r--docs/guides/federation/voting-by-itself.md16
3 files changed, 13 insertions, 12 deletions
diff --git a/docs/example.toml b/docs/example.toml
index 4078017..ce1ea83 100644
--- a/docs/example.toml
+++ b/docs/example.toml
@@ -154,9 +154,9 @@ htpasswd = "/etc/continuum/htpasswd"
# hand only through it (POST /admin/events/vote). It follows the `true` of the parties
# named (by default only on versions that only move to a checkpoint), votes `false` on a
# checkpoint proposed beside one it backs, if told, and proposes a checkpoint once it
-# holds so many events beyond its checkpoint, so many versions were written since, or so
-# long after it moved there; it backs and proposes none sooner than store-back-after
-# after a move or its start.
+# holds so many events beyond its checkpoint, so many versions changing more than moving
+# to a checkpoint were written since, or so long after it moved there; it backs and
+# proposes none sooner than store-back-after after a move or its start.
# store-vote-key = "/var/lib/continuum/party.key"
# store-vote-record = "/var/lib/continuum/party-record.json"
# store-follow = ["lass"]
diff --git a/docs/guides/federation/checkpoints.md b/docs/guides/federation/checkpoints.md
index ad468f8..c929d89 100644
--- a/docs/guides/federation/checkpoints.md
+++ b/docs/guides/federation/checkpoints.md
@@ -36,7 +36,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 were written since it (`--store-propose-versions`, after every version with 1),
+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,
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),
diff --git a/docs/guides/federation/voting-by-itself.md b/docs/guides/federation/voting-by-itself.md
index 2209389..b01bfd3 100644
--- a/docs/guides/federation/voting-by-itself.md
+++ b/docs/guides/federation/voting-by-itself.md
@@ -50,19 +50,19 @@ or `POST /admin/events/vote` with `{"proposal": "8d02…", "yes": true}`.
just started, it holds nothing for a while yet.
* **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 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
+ 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
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: 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.
+ 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.
* **`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.