From f85298c40c2528ee801c14a10a7db8920b50fdf8 Mon Sep 17 00:00:00 2001 From: tv Date: Thu, 19 Nov 2026 14:09:05 +0000 Subject: 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. --- docs/guides/federation/checkpoints.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'docs/guides/federation/checkpoints.md') 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), -- cgit v1.3.1