aboutsummaryrefslogtreecommitdiffstats
path: root/docs/federation.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-16 17:15:14 +0000
committertv <tv@krebsco.de>2026-11-16 18:29:32 +0100
commit0a5dc0ae08d43bc8c2d9945d15720ed58ca40fb9 (patch)
treee7d8dddd13a1f212b3d2b4c59482792ec5995f2c /docs/federation.md
parent11a2fad727e0075fa0f5a41cb9ef297a9b273ee6 (diff)
federation: what a checkpoint keeps is read as written under its version
An event doesn't name the version it was written under, and a node starting from a checkpoint holds none of the kept events' histories. It works out, but `start` has to assume it, and the text didn't say: a node reads what a checkpoint keeps as written under its version, as each was written under that one or an earlier and counts there, a kept proposal is on it, and a later `since` that leaves one out is past it.
Diffstat (limited to 'docs/federation.md')
-rw-r--r--docs/federation.md7
1 files changed, 5 insertions, 2 deletions
diff --git a/docs/federation.md b/docs/federation.md
index d64914c..3bcbcd6 100644
--- a/docs/federation.md
+++ b/docs/federation.md
@@ -426,8 +426,11 @@ it. A node that takes the version moves to the checkpoint: it builds it, forgets
everything before those heads that it doesn't keep, and every event not above them, and
refuses such events from then on. Judging an event after them needs nothing it forgot:
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
+with their votes all count, and are kept. A node starting from a checkpoint reads what
+it keeps as written under its version, as it holds none of their histories: each was
+written under that one or an earlier, counting there, a kept proposal is on it, and a
+later `since` that leaves one out is past it. 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). 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