diff options
| author | tv <tv@krebsco.de> | 2026-11-19 13:34:24 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-19 14:39:54 +0100 |
| commit | 9164ebfe9a4014cbbaaaff90c5a1d722e39457fd (patch) | |
| tree | 9a45156bd4919054939d12c97a19672e92e07b98 /docs/federation.md | |
| parent | 7a5aeb02024ddff71ba60f40913555cd21a633ad (diff) | |
federation: which nodes know a revision, in counts and before a `true`
`GET /events/counts` says, of each node a party lists, what it said it
speaks and knows (`knows`, by node ID): the wire versions, the oldest and
the newest, and the newest revision of the federation it knows, by
number and ID and as people read it, its number null where this
continuum doesn't know it; null where it said nothing, a build from
before SPEAKS or one the node didn't hear from; the node's own as it is.
So the nodes still to upgrade before a revision passes show, every
party's, where before a party's operators could check only their own.
A party's client, backing a proposal that moves to another revision,
warns of every node of any party not known to know it, a line a party
naming each and what it said: once it passes, those stop at it till
upgraded. `next` warns alike, of the revision it moves to, or of the
later one it suggests. A warning, not a refusal: what a node heard is
no proof, and a node not heard from may well be upgraded.
Diffstat (limited to 'docs/federation.md')
| -rw-r--r-- | docs/federation.md | 7 |
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. |
