summaryrefslogtreecommitdiffstats
path: root/docs/example.toml
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-19 01:48:57 +0000
committertv <tv@krebsco.de>2026-11-19 03:19:19 +0100
commit101080b8a62709cd2606dece086f959781bdf38f (patch)
tree618e9acdd6e5d311ece2cf5b213432257c31bc39 /docs/example.toml
parente0075264e9efdd4c8a32290c0d5643e7f48bfb14 (diff)
vote: a follower copies no false, lapses nothing others back, waits after a move
A node following a party (`--store-follow`) handed it more than the text said: * it copied the party's `false`: one party's nay freed bound followers, and its `true` shown to some and its `false` to the rest passed a checkpoint at one history and made it dead at another. It copies the `true` alone now, on any version too; * a checkpoint lapses every other proposal: the followed party ended any proposal it disliked by passing one. A node follows a checkpoint only where no proposal that changes more can still pass that someone but its proposer backs; * nothing bounded how often the store moved, so fresh events could be left out of every checkpoint; and a node just started held nothing for a while, so the voters' rule kept nothing. A node backs, and proposes, a checkpoint only once its store held its checkpoint, or ran, for a while (`--store-back-after`, ten minutes unless set), by itself or by hand. `federation.md` says what following hands over, and row 58 what a follower on any version copies; the guides and the example say the rest.
Diffstat (limited to 'docs/example.toml')
-rw-r--r--docs/example.toml8
1 files changed, 5 insertions, 3 deletions
diff --git a/docs/example.toml b/docs/example.toml
index 7f01df7..4bb5c98 100644
--- a/docs/example.toml
+++ b/docs/example.toml
@@ -151,10 +151,11 @@ htpasswd = "/etc/continuum/htpasswd"
# Behind the `federation` feature: this node votes and proposes for its party by itself
# (docs/federation.md, Votes a node casts by itself), with a key its party's version
# names, kept here, and its party's one record of its votes; its party then votes by
-# hand only through it (POST /admin/events/vote). It follows the parties named (by
-# default only on versions that only move to a checkpoint), votes `false` on a
+# 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, or so long after it moved there.
+# holds so many events beyond its checkpoint, 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"]
@@ -163,6 +164,7 @@ htpasswd = "/etc/continuum/htpasswd"
# store-propose-events = 10000
# store-propose-every = "7d"
# store-held-for = "10m"
+# store-back-after = "10m"
# SSH keys, as authorized_keys lines (ssh-ed25519 <base64> [comment]), whose signature
# on a strict remake's manifest this node takes: the values kept when the swarm turns