diff options
| author | tv <tv@krebsco.de> | 2026-11-19 14:11:39 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-19 15:18:45 +0100 |
| commit | 27b76d5748f23a879d9fc82c725a58b514020ef9 (patch) | |
| tree | d0201eed80c9c4a2db3f2e6281cac51dbc126ba6 /docs/guides | |
| parent | 8347900a553a3c4c9f9d3fc4a539fd31b41b07d3 (diff) | |
fork: a fork's check says what its version changes, rules among it
A node holding the history up to a fork's heads said whether it builds
the root, what it holds that those heads lack, and which parties' keys
the fork's version gives otherwise. A founder could change the rules, or
only their order, which says who writes where, and nobody joining was
shown it.
The check now says what the fork's version changes of the version
current at those heads, a line each as a proposal's are shown
(`client::changes`): `changes` in POST /events/fork, and
`continuum-party check` prints them. federation.md and the forking
guide say so, and that a fork's ID is compared whole: a founder trying
versions can steer its first few digits.
Diffstat (limited to 'docs/guides')
| -rw-r--r-- | docs/guides/federation/forking-and-following.md | 15 |
1 files changed, 11 insertions, 4 deletions
diff --git a/docs/guides/federation/forking-and-following.md b/docs/guides/federation/forking-and-following.md index ffc4fae..dafa974 100644 --- a/docs/guides/federation/forking-and-following.md +++ b/docs/guides/federation/forking-and-following.md @@ -55,14 +55,21 @@ A node holding the history up to the fork's heads builds its root and checks it: continuum-party --node http://lass:secret@localhost:3000 check fork-root # 7c55…: built here, byte for byte # its heads lack 0c7e… +# its version changes: +# changes: "3a90…" -> "b41f…" +# keys.makefu: {"keys":["ssh-ed25519 AAAA…"],"since":2} -> {"keys":[…],"since":5} +# nodes.lass: {"nodes":["continuum:9c07…"],"since":0} -> {…,"since":5} +# number: 4 -> 5 # makefu's keys: ["ssh-ed25519 AAAA…"] here, ["ssh-ed25519 AAAA…"] in the fork ``` Whether it builds that root at those heads; what it took that the heads lack (neither -among them, in their history, nor above them), which the fork doesn't hold; and, party by -party, the keys the fork's version gives otherwise than the party had at those heads. A -node that doesn't hold that history takes the root on its operator's word, who names the -fork by its ID. +among them, in their history, nor above them), which the fork doesn't hold; what the +fork's version changes of the one current at those heads, field by field, its rules and +their order among them, which say who writes where; and, party by party, the keys the +fork's version gives otherwise than the party had at those heads. A node that doesn't +hold that history takes the root on its operator's word, who names the fork by its ID: +compare that ID whole, as a founder trying versions can steer its first few digits. ## Following |
