From dd720b2556fa64bd07dc1d087b502ac4ab0f7899 Mon Sep 17 00:00:00 2001 From: tv Date: Thu, 19 Nov 2026 01:48:58 +0000 Subject: vote: propose a checkpoint after so many versions The votes cast before count at a history from before too: a proposal that died, or a rival, needs there only the votes it lacked, and after a close vote one key voting twice is enough, at any time until a checkpoint above the version that followed. Nodes that took that version refuse it; one lagging behind, or joining from the root, may take it. `federation.md` said it took the keys of two thirds of the parties. A node voting by itself proposes a checkpoint once so many versions were written since its store's (`--store-propose-versions`), as the design lists: with 1, after every version, so that what keys voting twice grow beside a version ends at a checkpoint above it. `federation.md` says how little a rival version takes, row 20 too, and the guides the option. --- docs/guides/federation/checkpoints.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) (limited to 'docs/guides/federation/checkpoints.md') diff --git a/docs/guides/federation/checkpoints.md b/docs/guides/federation/checkpoints.md index f935421..cd77e28 100644 --- a/docs/guides/federation/checkpoints.md +++ b/docs/guides/federation/checkpoints.md @@ -35,11 +35,12 @@ Like any version, it lapses the proposals on the version before: propose one whe 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`), or so long -after its store moved there (`--store-propose-every`), at the heads of what it held for -a while (`--store-held-for`, ten minutes unless set), 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. +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), +or so long after its store moved there (`--store-propose-every`), at the heads of what it +held for a while (`--store-held-for`, ten minutes unless set), 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. ## Backing one -- cgit v1.3.1