From b710146b9e17d844a1e2647a2b43eeadd62893aa Mon Sep 17 00:00:00 2001 From: tv Date: Thu, 19 Nov 2026 18:55:17 +0000 Subject: continuum-party: forks by what they are for, by a proposal, at the node's heads `fork` took a version written by hand and every head by name. Now: * fork FILE [HEAD...]: the heads the node shows where none are named; * fork proposal PROPOSAL: by the version of a proposal on the current version, as a fork's version is usually one that didn't pass; * fork admit, remove, give, take, keys, nodes, revision: by the next version changed as they say, as propose does (not checkpoint: a fork is at heads of its own); each subcommand taking --at HEAD... and --founder PARTY=NODE,..., which names a party's node list anew in the fork's version, so that the nodes its founders run it on are members there. --- docs/guides/federation/forking-and-following.md | 23 +++++++++++++++++------ 1 file changed, 17 insertions(+), 6 deletions(-) (limited to 'docs/guides/federation/forking-and-following.md') diff --git a/docs/guides/federation/forking-and-following.md b/docs/guides/federation/forking-and-following.md index 4890a61..63b7c40 100644 --- a/docs/guides/federation/forking-and-following.md +++ b/docs/guides/federation/forking-and-following.md @@ -19,23 +19,34 @@ go. The rules are the design's ([`federation.md`](../../federation.md), 1. **Choose the heads** it forks at: heads a node of yours showed (`heads` in `GET /events`) and has held for a while. The fork keeps what counts there; what was - written after them stays behind. -2. **Write the fork's version**: it changes the version current at those heads (that + written after them stays behind. Without heads named, the client forks at those the + node shows. +2. **Choose the fork's version**: it changes the version current at those heads (that version's hash as `changes`), numbered one past it. It names anew (`since` its number) the keys of any party whose keys it changes, and the founders' own node lists, so that their nodes are members there. It leaves out the parties that don't go, and may name those that weren't among the first to go, with their keys as they were, so that they can follow whenever they like. 3. **Make its root**, as a node holding that history builds it, with the events it - keeps: + keeps, to a file. The client writes the version as `propose` does, by what it is for + ([`common-changes.md`](common-changes.md)), here without lass, `--founder` naming the + founders' node lists anew, the nodes they run the fork on: ```sh - continuum-party --node http://tv:secret@localhost:3000 fork fork.json 4a1d… 9e30… \ + continuum-party --node http://tv:secret@localhost:3000 fork remove lass \ + --founder tv=continuum:1f0a… --founder makefu=continuum:83c2… > fork-root + ``` + + or by the version of a proposal that didn't pass, as often (`fork proposal 8d02`), or + by a version written by hand, at the heads given, by ID or prefix: + + ```sh + continuum-party --node http://tv:secret@localhost:3000 fork fork.json 4a1d 9e30 \ > fork-root ``` - The fork is named by its root's ID, the SHA-256 of its root (the file's first line), - which nobody can steer. + `--at 4a1d 9e30` names the heads for the others. The fork is named by its root's ID, + the SHA-256 of its root (the file's first line), which nobody can steer. 4. **Start it**: a node carries one swarm, so the founders start the fork's nodes with files of their own (state, document, store file), from the root (`--store-root fork-root`), or by its ID through one of them (`--store-id`), each -- cgit v1.3.1