From 8937eb571d805220f4f5cf3c8f4bd9b3bc84286d Mon Sep 17 00:00:00 2001 From: tv Date: Mon, 16 Nov 2026 17:14:56 +0000 Subject: federation: whether a checkpoint passed is the operator's to know Once a checkpoint passed, a node joins from a pinned one; but a node started from the root can't tell that one passed, as a chain old keys grew need name none. It is its operator's to know, not the node's to refuse. --- docs/federation.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/docs/federation.md b/docs/federation.md index 45e7e25..e431610 100644 --- a/docs/federation.md +++ b/docs/federation.md @@ -440,11 +440,12 @@ while the vote takes its course, a client writing once a checkpoint is proposed only on what is above its heads, and a party's client signs again what a move refused. **Joining.** Once a checkpoint passed, a node joins from a checkpoint its operator pins, -not from the root ([`store.md`](store.md), Pinned checkpoints). From the root, keys a -version named before it, revoked since or thrown away, could grow another chain, at -histories before the version that followed, and node lists naming only their own nodes -would seal a node joining in it, never shown the other. So a checkpoint bounds what old -keys can do to the versions after it. +not from the root ([`store.md`](store.md), Pinned checkpoints). Whether one passed is +its operator's to know, not the node's: a chain old keys grew need name none. From the +root, keys a version named before it, revoked since or thrown away, could grow another +chain, at histories before the version that followed, and node lists naming only their +own nodes would seal a node joining in it, never shown the other. So a checkpoint bounds +what old keys can do to the versions after it. A version that changes nothing but its number, what it changes and its checkpoint only moves the store on. Like any version, it lapses the proposals on the version before, so -- cgit v1.3.1