aboutsummaryrefslogtreecommitdiffstats
path: root/src/config/file.rs
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-19 03:48:03 +0000
committertv <tv@krebsco.de>2026-11-19 05:10:06 +0100
commit54bcc0e4ee8e1e6a29e0e01369c2ba95b27abce8 (patch)
tree20568ac1b47394ae9e603630fe1ab5464d1f7900 /src/config/file.rs
parente5f8df2a78f26d5928d1c96573dae5620dba5e25 (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 'src/config/file.rs')
0 files changed, 0 insertions, 0 deletions