aboutsummaryrefslogtreecommitdiffstats
path: root/docs/guides/federation/checkpoints.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-19 01:48:57 +0000
committertv <tv@krebsco.de>2026-11-19 03:18:49 +0100
commit03744437a5ffc36fbb5e973a0ddfd6b91945b212 (patch)
tree227eb42b4e7cac546b857cfacb79ab890e8bb137 /docs/guides/federation/checkpoints.md
parentf24063e90d02ef76d87401d6e74cf8c9f489ff7d (diff)
federation: votes on the events proposing a checkpoint above its heads
Anyone could propose a checkpoint's version again, by an event beside its heads. A node voting by itself, and a party's client, built a vote on every event proposing what it voted on, so every vote was beside the heads, and no version event written on them was taken: the checkpoint could never move the store. And the voters' rule refused it once that event was held for a while, as the heads left it out. They vote on the events proposing it that are above the heads it names (`State::proposing`), which `GET /events/counts` lists as `proposals`; where there are none, `none` says so, the node casts nothing and the client says why. The voters' rule leaves proposals and votes aside, as they lapse with the move. Row 70 is tested (`federation_attack_70`).
Diffstat (limited to 'docs/guides/federation/checkpoints.md')
-rw-r--r--docs/guides/federation/checkpoints.md12
1 files changed, 6 insertions, 6 deletions
diff --git a/docs/guides/federation/checkpoints.md b/docs/guides/federation/checkpoints.md
index 66f79e9..69debaf 100644
--- a/docs/guides/federation/checkpoints.md
+++ b/docs/guides/federation/checkpoints.md
@@ -43,12 +43,12 @@ is proposed; and it backs what it proposes.
## Backing one
Back a checkpoint only where everything you held for a while before it was proposed is
-among its heads, in their history, or above them: heads a proposer made up, built on
-little, would take back what was written since, a key set dropping a stolen key among
-it. A node voting by itself backs one only so, and so does a vote by hand through it
-(`continuum-party vote … --through`). A party's client voting on its own
-(`continuum-party vote`) checks no heads: check them yourself, or vote through such a
-node.
+among its heads, in their history, or above them, proposals and votes aside, which lapse
+with the move: heads a proposer made up, built on little, would take back what was
+written since, a key set dropping a stolen key among it. A node voting by itself backs one
+only so, and so does a vote by hand through it (`continuum-party vote … --through`). A
+party's client voting on its own (`continuum-party vote`) checks no heads: check them
+yourself, or vote through such a node.
* `--store-follow PARTY,…` has a node voting by itself follow those parties' votes, by
default on versions that only move to a checkpoint, and still by that rule.