From aa77c10a8a20356c277e511e9c6e33c98c9b4104 Mon Sep 17 00:00:00 2001 From: tv Date: Wed, 18 Nov 2026 11:47:42 +0000 Subject: guides: a party writes its node list without a vote Where a reader adding a node looks (getting started, proposing a version, who syncs), the guides say that a party writes its node list itself, signed with a key its version names, and link to how; a version names a list anew only where its party can't. --- docs/guides/federation/getting-started.md | 3 ++- docs/guides/federation/proposing-and-voting.md | 15 ++++++++++----- docs/guides/federation/running-a-node.md | 8 +++++++- 3 files changed, 19 insertions(+), 7 deletions(-) diff --git a/docs/guides/federation/getting-started.md b/docs/guides/federation/getting-started.md index 3570ee3..6f1693c 100644 --- a/docs/guides/federation/getting-started.md +++ b/docs/guides/federation/getting-started.md @@ -105,7 +105,8 @@ continuum --store-id 6d1e… --store-party lass --store-file store.json \ ``` Nodes sync with the nodes the parties list, and with no others: both are in the first -version. +version. A party lists another node of its own by itself, without a vote +([`common-changes.md`](common-changes.md#what-a-party-does-by-itself)). ## Writing and reading diff --git a/docs/guides/federation/proposing-and-voting.md b/docs/guides/federation/proposing-and-voting.md index 8c9c66f..5330b06 100644 --- a/docs/guides/federation/proposing-and-voting.md +++ b/docs/guides/federation/proposing-and-voting.md @@ -1,9 +1,11 @@ # Proposing and voting -Everything a federation decides is a change of its policy: who the parties are, their -keys and node lists, who writes where, a checkpoint. A party proposes a version, the -parties vote, and once two thirds of them back it, it is written. The rules are the -design's ([`federation.md`](../../federation.md), The policy, Changing the policy). +Everything a federation decides is a change of its policy: who the parties are, the keys +they vote with, who writes where, a checkpoint. A party proposes a version, the parties +vote, and once two thirds of them back it, it is written. The rules are the design's +([`federation.md`](../../federation.md), The policy, Changing the policy). A party's +node list and its key set are its own to write, without a vote +([`common-changes.md`](common-changes.md#what-a-party-does-by-itself)). ## Writing a version @@ -24,7 +26,10 @@ Then change it: its `since`; every other keeps the `since` it had, and its keys unchanged. A party left out is no party any more. * **`nodes`**: every party's node list, with its `since`, likewise. The version letting a - party in names its list anew, empty where it gives it no nodes. + party in names its list anew, empty where it gives it no nodes. Otherwise a version + names a list anew only where its party can't write its own, with a key the current + version names for it: a party adds and takes off its nodes by itself + ([`common-changes.md`](common-changes.md#what-a-party-does-by-itself)). * **`rules`**: in order, the first matching a path deciding who writes there ([`writing-and-reading.md`](writing-and-reading.md), Places). * **`checkpoint`**, only where the version moves the store to a checkpoint: the heads. diff --git a/docs/guides/federation/running-a-node.md b/docs/guides/federation/running-a-node.md index af16594..371bd10 100644 --- a/docs/guides/federation/running-a-node.md +++ b/docs/guides/federation/running-a-node.md @@ -15,7 +15,8 @@ what its API lets in, and joining. Joining with an empty document, the node takes as its root that store's genesis change only. * `--store-party NAME`, which both need: the party the node is of, named in its entry - and its handshakes. It is a member once that party's node list names it. + and its handshakes. It is a member once that party's node list names it + ([Who syncs](#who-syncs)). * `--store-file PATH`: what is the node's own, written whenever it changes: the events it refused by what it took before (of two versions changing one, the second it judged) and those its operator had it drop. A node reads its store anew from its document @@ -50,6 +51,11 @@ its log (`This node isn't a member of its store`); once it is listed, the others with it (`This node is a member of its store`). A party that takes a node off its list takes it out of the swarm. +A party writes its node list itself, without a vote, signed with a key its version names +(`continuum-party nodes`, +[`common-changes.md`](common-changes.md#what-a-party-does-by-itself)): a node it adds +is a member as soon as the list is taken. + Of a node's neighbours (`--neighbours`), some are kept among the members of its own party and of the parties in `--store-neighbour-parties`, by the graph among those alone, so that a party listing many nodes can't be all of a node's neighbours. -- cgit v1.3.1