diff options
| author | tv <tv@krebsco.de> | 2026-11-19 14:09:05 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-19 15:18:42 +0100 |
| commit | f85298c40c2528ee801c14a10a7db8920b50fdf8 (patch) | |
| tree | 1eef6e26be145d819b5280142f9a6aa277ec4b3f /docs/guides/federation/voting-by-itself.md | |
| parent | 59d8d6f9c4f539ac9392872026d99a93f66102ee (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/guides/federation/voting-by-itself.md')
| -rw-r--r-- | docs/guides/federation/voting-by-itself.md | 16 |
1 files changed, 8 insertions, 8 deletions
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. |
