From 27b76d5748f23a879d9fc82c725a58b514020ef9 Mon Sep 17 00:00:00 2001 From: tv Date: Thu, 19 Nov 2026 14:11:39 +0000 Subject: 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. --- docs/federation.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'docs/federation.md') diff --git a/docs/federation.md b/docs/federation.md index f36eabd..e47da93 100644 --- a/docs/federation.md +++ b/docs/federation.md @@ -619,12 +619,14 @@ store of its own from the federation's ([`store.md`](store.md), [Forks](store.md heads with that version current. Every proposal is a chance to fork: the version is usually one that didn't pass. 2. A fork is named by its root's ID, which nobody can steer to a given name, the - federation it came from least of all. It takes only events with its root in their + federation it came from least of all; a few of its first digits can be, by trying + versions, so an ID is compared whole. It takes only events with its root in their history: what the stayers sign after it isn't taken there, nor what the fork's parties sign after it in the federation they left. 3. The others join it as a node joins any swarm, by its ID. A node holding the history up to those heads builds the root and checks it, says what it holds that those heads - lack, and, party by party, whether the fork's version gives it the keys it had there: + lack, what the fork's version changes of the one current there, its rules and their + order among it, and, party by party, whether it gives the party the keys it had there: a founder may give a party that didn't go keys of its own. A node that doesn't hold that history takes the root on its operator's word, as its operator names the fork. -- cgit v1.3.1