diff options
Diffstat (limited to 'docs/guides/federation/upgrades.md')
| -rw-r--r-- | docs/guides/federation/upgrades.md | 11 |
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. |
