diff options
| author | tv <tv@krebsco.de> | 2026-11-16 04:13:43 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-16 04:13:43 +0000 |
| commit | 2377063b455aaf4b629e1bce372d55fd05c214c1 (patch) | |
| tree | 7b16d1927a41f5ff4674ab798bec4be7b4aaa43b /docs/federation.md | |
| parent | 20aaea68e4e3839e10655017ff06cc7134646415 (diff) | |
federation: a federation's genesis built from its first version
A federation's genesis change, judged by none, was its founding node's:
what else it held (values at places, votes) nobody checked, and the
swarm's name was the one its node drew or remembered, so two federations
started under one name took each other's envelopes. It is built byte for
byte from the first version alone, as a fork's genesis is from its
version and heads, and holds the policy, the swarm's name, the version
and what it sets, nothing else; the swarm is named by the version's
hash, and a node joining builds the genesis and checks it. The genesis
writes no topology: a federated swarm runs continuum's own.
Diffstat (limited to 'docs/federation.md')
| -rw-r--r-- | docs/federation.md | 42 |
1 files changed, 24 insertions, 18 deletions
diff --git a/docs/federation.md b/docs/federation.md index d8a325f..3acde81 100644 --- a/docs/federation.md +++ b/docs/federation.md @@ -216,14 +216,14 @@ A federated swarm has no user registry, and of `_continuum` takes only these wri * by an epoch's first change (the genesis change, a remake's snapshot): epochs and the swarm's ID. -Everything else is closed, a write at, within or above it refused: users, bans, -logouts, sessions, forgotten nodes, `_continuum/access` with the policy's place, the -swarm's topology (`neighbours`, `relays`, `topology`, `dissemination`), and whatever a -later continuum adds. The topology stays as the genesis change set it; each node picks -its own relays, and some of its neighbours by party (Nodes). Nothing but the policy is -read of the rest. A member's change carries its node's signature, as signatures are -required in a strict swarm. A party logs in to its own nodes as its operator sets up, -and a node takes tokens only from the nodes of its own party (Nodes). +Everything else is closed, a write at, within or above it refused: users, bans, logouts, +sessions, forgotten nodes, `_continuum/access` with the policy's place, the swarm's +topology (`neighbours`, `relays`, `topology`, `dissemination`), and whatever a later +continuum adds. The topology is continuum's own, as the genesis change writes none; each +node picks its own relays, and some of its neighbours by party (Nodes). Nothing but the +policy is read of the rest. A member's change carries its node's signature, as +signatures are required in a strict swarm. A party logs in to its own nodes as its +operator sets up, and a node takes tokens only from the nodes of its own party (Nodes). ### Changing the policy @@ -454,16 +454,20 @@ for parties, zones, blocks and names that are nobody's by their spelling. ### Starting a federation A federation starts with a swarm of its own: its genesis change, the swarm's first, -writes the federated policy and the first version, with the key sets and node lists it -sets, among them the list of its own node's party, naming that node: so the federation -starts with members, and other nodes come in as their parties list them. It records -them as a swarm strict from its start records its policy (`--bootstrap-policy`) -*(checked: `swarm::bootstrap`)*, which starts it empty: content before it would be a -change from before the federation, judged by none. So nothing is from before the -federation, and nothing writes the policy's place after the genesis change: the -federation changes by versions, and is left by a fork. A running swarm doesn't become -federated; its parties start one, and sign into it, after the genesis change, what they -keep. +holds the federated policy, the swarm's name and the first version, with the key sets +and node lists it sets, and nothing else; among those lists, one naming a node of its +founders', so the federation starts with members, and other nodes come in as their +parties list them. It is built byte for byte from the first version alone, as a fork's +genesis is from its version and heads (Forks): its writer from the swarm's name, time 0, +no message; and the swarm is named by the first version's hash, so one first version +makes one swarm, and a node joining builds the genesis change and checks it. A swarm +strict from its start records its policy in its genesis change too +(`--bootstrap-policy`) *(checked: `swarm::bootstrap`)*, which starts it empty: content +before it would be a change from before the federation, judged by none. So nothing is +from before the federation, and nothing writes the policy's place after the genesis +change: the federation changes by versions, and is left by a fork. A running swarm +doesn't become federated; its parties start one, and sign into it, after the genesis +change, what they keep. ### Remakes @@ -660,6 +664,8 @@ What an attacker does, and what happens. *Unit*: the judging, with crafted chang | 70 | A path whose `{party}` segment names no party (`names/r/foo`) | The `{party}` rule doesn't match; a later rule decides | unit | | 71 | A map made where no `@` key is written below it, or where one is (hiding what it holds) | Refused | unit | | 72 | A party's first envelope at a place another's envelope holds | Names that one as `prev`, its `seq` one more; anew, refused | unit | +| 73 | A federation's genesis change holding more than its first version gives (values, votes, a topology) | A node joining builds it and doesn't join one that differs | sim | +| 74 | Two federations started under one swarm name | None: a federation is named by its first version's hash | unit | ## Roads not taken |
