diff options
| author | tv <tv@krebsco.de> | 2026-11-19 03:48:03 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-19 05:10:06 +0100 |
| commit | 54bcc0e4ee8e1e6a29e0e01369c2ba95b27abce8 (patch) | |
| tree | 20568ac1b47394ae9e603630fe1ab5464d1f7900 /docs/guides/federation/when-things-go-wrong.md | |
| parent | e5f8df2a78f26d5928d1c96573dae5620dba5e25 (diff) | |
federation: a version names the revision of federation 1 it follows
What every node must agree on was named by the federation's number alone, and a change
that only took more kept it: a party could use it before every node ran it, and nodes
not upgraded refused what followed and parted from the others.
A version now names the revision it follows by its ID (`"revision": "<ID>"`), the
SHA-256 of the JCS list of the features it adds to the base revision federation 1 began
with (`federation::revision`); a version naming none follows the base revision, ECDSA
keys among it, so the versions written so far read as they did. A version names the base
revision only by leaving `revision` out, and a revision no earlier than the one of the
version it changes. A continuum that doesn't know a revision, another build's among
them, can't read a version naming it: it stops at a version event writing one, and says
which revision and what it knows. There are no revisions yet but the base revision.
`federation.md` says how a revision is rolled out, then passed, and what a later
continuum may leave out; the upgrades guide, and the one on a node stopped, alike.
Diffstat (limited to 'docs/guides/federation/when-things-go-wrong.md')
| -rw-r--r-- | docs/guides/federation/when-things-go-wrong.md | 11 |
1 files changed, 6 insertions, 5 deletions
diff --git a/docs/guides/federation/when-things-go-wrong.md b/docs/guides/federation/when-things-go-wrong.md index fad11c5..8171201 100644 --- a/docs/guides/federation/when-things-go-wrong.md +++ b/docs/guides/federation/when-things-go-wrong.md @@ -78,13 +78,14 @@ can't judge`), and `GET /events` names the event, why, and how many it holds bac ```sh curl -s -u tv:secret localhost:3000/events | jq -r .stopped.why -# version 3c0f… passed, and doesn't read as one here: of federation 2, and this -# continuum knows 1 alone +# version 3c0f… passed, and doesn't read as one here: revision 9f2c…, which this +# continuum doesn't know, as it knows the base revision alone: a release that knows it +# reads this version ``` -`why` says what doesn't read: a federation this continuum doesn't know, a field it -doesn't know, by its name, a key of a type it doesn't take, or whatever else makes a -version none ([`proposing-and-voting.md`](proposing-and-voting.md), +`why` says what doesn't read: a federation or a revision this continuum doesn't know, a +field it doesn't know, by its name, a key of a type it doesn't take, or whatever else +makes a version none ([`proposing-and-voting.md`](proposing-and-voting.md), [Writing a version](proposing-and-voting.md#writing-a-version)). Upgrade the node to a continuum that reads it: restarted, it reads its store anew and |
