aboutsummaryrefslogtreecommitdiffstats
path: root/docs/federation.md
diff options
context:
space:
mode:
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 8dc23b3..615bc05 100644
--- a/docs/federation.md
+++ b/docs/federation.md
@@ -904,8 +904,11 @@ swarm's root names holds no store, and says so.
So a revision is rolled out, then passed: every party's operators restart its nodes on a
continuum that knows it, and the parties pass a version naming it once theirs do, as a
-party's client backs no version it doesn't read. Who hasn't by then stops at that version,
-and takes part again once it has. Once a store moved to a checkpoint at a version naming
+party's client backs no version its node doesn't read. Each node tells its peers the
+newest revision it knows (SPEAKS, [`peers.md`](peers.md),
+[Handshake and join](peers.md#handshake-and-join)), and a party's client warns, backing
+one, of every node a party lists not known to know its revision. Who hasn't upgraded by
+then stops at that version, and takes part again once it has. Once a store moved to a checkpoint at a version naming
a revision, nodes join it only from a pinned checkpoint, and nobody judges what came
before again: a later continuum may hold only stores at that revision or after, and leave
out the rules of the revisions before.