aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-16 16:40:46 +0000
committertv <tv@krebsco.de>2026-11-16 18:01:48 +0100
commit7dbf7dec7556e24e95ec5576c1bd290874a5d7c0 (patch)
tree33ef9784192290fcd9830c254b4ac2024cf46716
parent1ef097ecbb81f1478cbb9ca13b4c263a56315ac5 (diff)
federation: a node starting from a checkpoint judges the version naming it
A node starting from a checkpoint its operator pins holds neither the checkpoint before it nor the events between, so it can't check that the version naming its checkpoint names heads after the one current at that version, at which that one is current too. It takes that on its operator's word, and so takes the version, as every node did.
-rw-r--r--docs/federation.md5
1 files changed, 4 insertions, 1 deletions
diff --git a/docs/federation.md b/docs/federation.md
index 98d2eee..e2f83e1 100644
--- a/docs/federation.md
+++ b/docs/federation.md
@@ -412,7 +412,10 @@ refuses such events from then on. Judging an event after them needs nothing it f
the version, every party's keys and node list, and the proposals on the current version
with their votes all count, and are kept. A node that can't build a checkpoint, as it
was away across a move and a remake after it, or as it joins, takes it only where its
-operator pins it ([`store.md`](store.md), Pinned checkpoints).
+operator pins it ([`store.md`](store.md), Pinned checkpoints). What it can't check of
+its heads it takes on its operator's word: that they are after the checkpoint current at
+the version naming them, at which that one is current too; so it judges that version as
+every node does.
What a checkpoint loses: what counted no more before it, so that a key added back, or a
place given back, brings back nothing signed before it, and a party that voted twice on