From ff2da13601f8055d037758fd8c1056db6185f106 Mon Sep 17 00:00:00 2001 From: tv Date: Mon, 16 Nov 2026 10:40:42 +0000 Subject: federation: wordings left from the last changes A version's `since`, where it doesn't name a party's keys or list anew, is the `since` the version it changes gives the party, not that version's number. A version written again is one a node took, and every node takes it however often it is written. A forked writer's nodes are apart until operators have one side drop what it took, or a fork. And a fork's genesis leaves out continuum's own data, earlier epochs' metadata among it, which a second clause said again. --- docs/federation.md | 41 +++++++++++++++++++++-------------------- 1 file changed, 21 insertions(+), 20 deletions(-) (limited to 'docs') diff --git a/docs/federation.md b/docs/federation.md index 8eefffb..bc3b514 100644 --- a/docs/federation.md +++ b/docs/federation.md @@ -156,8 +156,8 @@ current at its heads, Forks). Spread out: version. With them the party signs its votes and proposals on this version, its key set and its node list (Keys, Nodes). Its `since` is the number of the version that named them anew: this one's where it does (a party new in it, keys the parties - replace, or the same keys named anew), else that of the version it changes, whose - keys for the party it then names unchanged. + replace, or the same keys named anew), else the `since` the version it changes gives + the party, whose keys it then names unchanged. * **The node lists** (`nodes`), by party, each a list of node IDs with its `since` as keys have one, for the parties a version named one for anew, this or an earlier one: the first version and a fork's name those of the parties that start it (Nodes). A @@ -284,8 +284,8 @@ node's refusal doesn't make it drop what it took. One valid at its history break rule: its committer isn't refused as a whole, as a member whose own change broke a rule is ([`access.md`](access.md)), and the node reports it apart from changes against the rules. Of two that change the one it reads, it takes the first it judges. Without keys -voting twice, every version written changes the one every node reads, and none is -refused. +voting twice, every version written changes the one every node reads, or is one it took, +and none is refused. **An operator may have its node drop what it took**: a version the others refused, or any change, with everything built on it, as continuum drops a change its node took and @@ -426,17 +426,17 @@ the group won't follow passed, the parties can't agree, or it leaves the federat read as at heads it names, each place's value as the federation reads it (The design), built byte for byte from the fork's first version and those heads alone, with the swarm's Automerge version: its writer from the fork's name, time 0, no - message, nothing of a remake's metadata but what the heads fix; so one version and - one set of heads make one swarm, and a node with an empty document takes it on its - peers' word, as it takes an epoch. It holds all of it but for what a snapshot leaves - out, by the version current at those heads (Remakes), the federation's versions, and - continuum's own data (member entries, remake records and acks, earlier epochs' - metadata, the swarm's name): of versions, only the group's own, the fork's first. It - names the highest version at those heads as the one it changes, is numbered one past - it, and names anew the node lists of the parties that start it, and the keys of any - party whose keys it changes; judged by none, as an epoch's first change is. Every - proposal is a chance to fork: the version is usually one that didn't pass. To leave - the federation, the genesis holds another policy instead, and what it needs. + message; so one version and one set of heads make one swarm, and a node with an empty + document takes it on its peers' word, as it takes an epoch. It holds all of it but + for what a snapshot leaves out, by the version current at those heads (Remakes), the + federation's versions, and continuum's own data (member entries, remake records and + acks, earlier epochs' metadata, the swarm's name): of versions, only the group's own, + the fork's first. It names the highest version at those heads as the one it changes, + is numbered one past it, and names anew the node lists of the parties that start it, + and the keys of any party whose keys it changes; judged by none, as an epoch's first + change is. Every proposal is a chance to fork: the version is usually one that didn't + pass. To leave the federation, the genesis holds another policy instead, and what it + needs. 2. A fork is named by the hash of its first version together with the heads it names, which nobody can steer to a given name, the old swarm's least of all: its genesis change writes it at `_continuum/swarm`, as every node checks, and an envelope's meta @@ -617,9 +617,10 @@ long nodes stay together. `true` and `false` for it are both there, and two proposals on one version pass only where some party backed both while neither was dead, or some party's `true` and `false` on one of them are both there. Without keys voting twice, at most one version - changes a version, and every node takes it; keys an earlier version named move no - node that took the version after it. With them, each node keeps the version it took, - nodes holding the same changes still read the same policy, and the parties fork. + changes a version, and every node takes it, however often it is written; keys an + earlier version named move no node that took the version after it. With them, each + node keeps the version it took, nodes holding the same changes still read the same + policy, and the parties fork. 3. **Remakes.** A node follows a remake only where it built the snapshot itself, from a base it holds, a member there, the version it reads written there; its peers' word never moves it. What came after, under that version, is replayed in history's order, @@ -676,7 +677,7 @@ What an attacker does, and what happens. *Unit*: the judging, with crafted chang | 36 | A write after a base on what the snapshot left out, or naming a version before the base's | Quarantined; its party writes again | unit | | 37 | A node with an empty document handed a made-up epoch | Taken. Not promised | sim | | 38 | A coordinator remakes often, or a party never acks | Slow, not wrong; the others fork | sim | -| 39 | A writer forked: two changes, one number | Honest nodes split until a fork. Not promised | sim | +| 39 | A writer forked: two changes, one number | Honest nodes split until operators have one side drop what it took, or a fork. Not promised | sim | | 40 | Different changes to different peers | Honest nodes agree once they sync, but where keys voted twice, a coordinator decided two remakes for one epoch, or a writer forked | sim | | 41 | A party withholding its changes or votes | Not promised | — | | 42 | Flooding: namespace, proposals, history | Slow, not wrong | bench | @@ -697,7 +698,7 @@ What an attacker does, and what happens. *Unit*: the judging, with crafted chang | 57 | Content written before a federation's genesis change, and a change built on it | None: the genesis change is the swarm's first | unit | | 58 | A federation's genesis change whose first version lists no node | Nothing after it is taken: no node is a member | unit | | 59 | A version replacing every listed party's keys | The lists still count, each its party's until it writes another | unit | -| 60 | A version whose `since` for a party is neither its own number nor that of the version it changes, or that changes a party's keys or list without naming them anew | No version: refused written as one | unit | +| 60 | A version whose `since` for a party is neither its own number nor the `since` the version it changes gives the party, or that changes a party's keys or list without naming them anew | No version: refused written as one | unit | | 61 | A version written again late, at a history from before the next, by a member that was away | Taken: it is one every node took | unit | | 62 | A proposal whose text doesn't hash to its place | Refused | unit | | 63 | An honest member writes a version valid where it is written, on the side a node doesn't read | Refused, and reported apart; its committer isn't refused as a whole | unit | -- cgit v1.3.1