aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/federation.md11
1 files 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