aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-16 03:11:42 +0000
committertv <tv@krebsco.de>2026-11-16 03:11:42 +0000
commitab9e29c9290dcf7faf535b554932ee32a793119c (patch)
tree3a03cc433dfd6218b06f8e61a7b1e4e66a85596a /docs
parenta26ae757f6ec7c86940233e2e4492e11bf443012 (diff)
federation: a fork taken only on history a node holds
A node holding the old document left an epoch only for one it built itself, but took a fork's heads' history, where it lacked some, on its peers' word: a founder could name heads holding a change it sent nobody, a version written without votes say, and the genesis would carry what that change set. A node holding the old document takes a fork only where it holds the heads' history, syncing what it lacks from the old swarm, each change judged there; otherwise it says it can't check and leaves it to its operator. Only a node with an empty document takes a fork on its peers' word, as it takes an epoch.
Diffstat (limited to 'docs')
-rw-r--r--docs/federation.md31
1 files changed, 17 insertions, 14 deletions
diff --git a/docs/federation.md b/docs/federation.md
index 6c7d9ba..be2251c 100644
--- a/docs/federation.md
+++ b/docs/federation.md
@@ -386,16 +386,16 @@ the group won't follow passed, the parties can't agree, or it leaves the federat
read as at heads it names, 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 that doesn't hold the
- heads' history takes it on its peers' word, as a node with an empty document takes
- an epoch. It holds all of it but for what a snapshot leaves out (Remakes), the
- federation's versions, continuum's member entries and the swarm's name: of versions,
- only the group's own, the fork's first, with the key sets and node lists it sets. It
- names the highest version at those heads as the one it changes, is numbered one past
- it, and sets the node lists of the parties that start it, and the keys of any party
- it names anew; 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.
+ 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 (Remakes), the federation's versions, continuum's member entries
+ and the swarm's name: of versions, only the group's own, the fork's first, with the
+ key sets and node lists it sets. It names the highest version at those heads as the
+ one it changes, is numbered one past it, and sets the node lists of the parties that
+ start it, and the keys of any party it names anew; 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
@@ -403,10 +403,12 @@ the group won't follow passed, the parties can't agree, or it leaves the federat
count, whatever swarm they name; beyond them, nothing signed for one swarm is taken
in another.
3. The others join it as a node joins any swarm, by its genesis change's hash. A node
- that holds the old document checks the new one against it first, the same at those
- heads but for what step 1 leaves out; says what it holds that those heads lack; and
- says, party by party, whether the fork's version gives it the keys it had there: a
- founder may give a party that didn't go keys of its own.
+ that holds the old document takes it only where it holds the heads' history, syncing
+ what it lacks from the old swarm, each change judged there; otherwise it says it
+ can't check, and leaves it to its operator. It checks the new one against the old
+ first, the same at those heads but for what step 1 leaves out; says what it holds
+ that those heads lack; and says, party by party, whether the fork's version gives it
+ the keys it had there: a founder may give a party that didn't go keys of its own.
A fork needs nobody's vote and nobody's ack: it binds only those who go, and the swarm
they left goes on for those who stay. A party the fork's version leaves out writes
@@ -624,6 +626,7 @@ What an attacker does, and what happens. *Unit*: the judging, with crafted chang
| 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 |
| 64 | Nodes reinstalled under new IDs, their old entries left behind | Each counts no more, and the next snapshot leaves it out | unit |
+| 65 | A fork at heads holding a change sent to nobody (a version written without votes, say) | A node holding the old document takes the fork only where it holds the heads' history, each change judged | sim |
## Roads not taken