1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
|
# Upgrades and the federation's number
Upgrading the continuum a federated swarm's nodes run, and what the federation's number
in each version says. The rules are the design's ([`federation.md`](../../federation.md),
[Changing the federation](../../federation.md#changing-the-federation)).
## Upgrading continuum
A node of a federated swarm upgrades as any node does
([`operations.md`](../../operations.md), [Upgrading](../../operations.md#upgrading)): one
at a time, restarted with its files. Across a change of the wire format, upgraded nodes
and the others don't talk, and the swarm is split until all are upgraded; a remake needs
the same Automerge on every node, and one with another rejoins instead of switching. Until
continuum's first release, take every upgrade as such a change.
Nobody runs every node of a federated swarm: each party's operators upgrade its nodes.
Agree on when, among the parties, and upgrade close together.
## The federation's number and its revision
What every node must agree on, byte for byte, is named by the federation's number,
which every version gives (`"federation": 1`), and its revision: the rules, how an event,
a version and a checkpoint are spelled, signed and judged, what the events read as, and,
on Automerge, what the document holds, what a change writes, the genesis change built from
the root, the snapshot, and the Automerge version, whose encoding fixes a change's hash.
Their 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. 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.
What is judged at an event's history changes by a revision of federation 1, which a
version names by its ID (`"revision": "<ID>"`); a version naming none follows the base
revision, `ecdsa-sha2-nistp256` keys beside Ed25519 ones among it. There are none yet but
the base revision. A node that doesn't know the revision a version names reads it as it
reads one of another federation: none, and it stops at a version event writing it. What a
revision adds is taken only under a version naming it, which two thirds pass, so no party
uses it early: roll it out first, every party's operators upgrading their nodes, then pass
a version naming it.
What no history judges, the document, a change and the snapshot, no version names: a
change there splits the swarm until every node runs it (above).
|