aboutsummaryrefslogtreecommitdiffstats
path: root/docs/guides/federation/upgrades.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-18 18:49:50 +0000
committertv <tv@krebsco.de>2026-11-18 20:29:41 +0100
commitc64fcc05d8c53bee99ab039bd709039afb730cdd (patch)
tree45baad78d7b92de42283be2954fc3f9b4dd6129d /docs/guides/federation/upgrades.md
parent598366b03679eac9d04f32d9194f3ba4ba9c3da8 (diff)
federation: a node stops at a version it doesn't read
A version event writing a proposal passed on the version a node reads, which doesn't read as a version there (of a later federation, using what a later continuum takes, or none at all), the node can't judge: `Fold::stops`. The store stops at it: it takes nothing and refuses nothing from then on, holding back whatever comes, that event first (`Offered::Stopped`), and keeps none of it across a restart, where it stops there again. One beside the version the node reads is refused of its own, as any other. Its operator has it drop that event (`POST /admin/events/drop`), or one it builds on: it is refused as dropped, or as built on what was, any version event writing that version with it, kept in the store file; the node judges what it held back and goes on under the version before. Allowed again, it stops there once more. The node logs the stop and its end; `GET /events` names the event, why, and how many it holds back (`stopped`); a put answers `stopped`, written into the document all the same; a node voting by itself casts nothing while stopped. The test fold's eras tagged `new` stop a store. Row 39 is tested (`federation_attack_39`); of rows 9, 10 and 48, a node stops at the version event.
Diffstat (limited to 'docs/guides/federation/upgrades.md')
-rw-r--r--docs/guides/federation/upgrades.md11
1 files changed, 7 insertions, 4 deletions
diff --git a/docs/guides/federation/upgrades.md b/docs/guides/federation/upgrades.md
index 570de19..f91143f 100644
--- a/docs/guides/federation/upgrades.md
+++ b/docs/guides/federation/upgrades.md
@@ -26,8 +26,11 @@ the snapshot, and the Automerge version, whose encoding fixes a change's hash. T
bytes are fixed by vectors that the tests check (`federation::vectors`).
There is one federation, 1. A node knows it alone: a version naming another is none to
-it, refused where a version event names it, with everything built on it. A proposal
-naming another is taken as a proposal, and a party's client backs none.
+it. Where one passes, the node stops at the version event writing it, taking nothing and
+refusing nothing, until it runs a continuum that knows it, or its operator has it drop
+that event ([`when-things-go-wrong.md`](when-things-go-wrong.md),
+[A node stopped](when-things-go-wrong.md#a-node-stopped)). A proposal naming another is
+taken as a proposal, and a party's client backs none.
A change to any of that is a federation of its own, with the next number, and its own
design. A swarm moves to it by a version naming it, which the parties pass once their
@@ -37,5 +40,5 @@ A change that only has the federation take what it refused, and reads nothing it
otherwise, keeps the number: `ecdsa-sha2-nistp256` keys beside Ed25519 ones. Roll it out
first, then use it: every party's operators upgrade their nodes, and only then does a
party name such a key in a version or a key set, or sign with one. A node not upgraded
-refuses what uses it and reads otherwise than the others: a version naming such a key is
-none to it, and it stays on the version before.
+refuses what uses it and reads otherwise than the others; at a version naming such a key,
+none to it, it stops, until it is upgraded.