aboutsummaryrefslogtreecommitdiffstats
path: root/docs/federation.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/federation.md')
-rw-r--r--docs/federation.md17
1 files changed, 9 insertions, 8 deletions
diff --git a/docs/federation.md b/docs/federation.md
index 41c195e..d8a325f 100644
--- a/docs/federation.md
+++ b/docs/federation.md
@@ -402,14 +402,15 @@ the group won't follow passed, the parties can't agree, or it leaves the federat
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 (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.
+ 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, 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