aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/federation.md30
1 files changed, 16 insertions, 14 deletions
diff --git a/docs/federation.md b/docs/federation.md
index 0ddb4bd..72bcca1 100644
--- a/docs/federation.md
+++ b/docs/federation.md
@@ -431,20 +431,22 @@ for a fork (Forks). This is the voter's rule, by its own clock: nothing more is
It is a version only where its proposal is above those heads, and a version event
writing it is taken only where it is above them too, and so is every vote it is written
on ([`store.md`](store.md), Events): so moving to the checkpoint refuses nothing that
-decided it. A vote beside them binds its party as any yes does, until the move refuses
-it. A node that takes the version moves to the checkpoint: it builds it, forgets
-everything before those heads that it doesn't keep, and every event not above them, and
-refuses such events from then on. Judging an event after them needs nothing it forgot:
-the version, every party's keys and node list, and the proposals on the current version
-with their votes all count, and are kept. A node starting from a checkpoint reads what
-it keeps as written under its version, as it holds none of their histories: each was
-written under that one or an earlier, counting there, a kept proposal is on it, and a
-later `since` that leaves one out is past it. A node that can't build a checkpoint, as
-it was away across a move and a remake after it, or as it joins, takes it only where its
-operator pins it ([`store.md`](store.md), Pinned checkpoints). What it can't check of
-its heads it takes on its operator's word: that they are after the checkpoint current at
-the version naming them, at which that one is current too; so it judges that version as
-every node does.
+decided it. A party's client, and a node voting by itself, vote on the events proposing
+what they vote on, and a node proposes a checkpoint on its heads: so their votes are
+above those heads wherever the proposal is. A vote beside them binds its party as any
+yes does, until the move refuses it. A node that takes the version moves to the
+checkpoint: it builds it, forgets everything before those heads that it doesn't keep,
+and every event not above them, and refuses such events from then on. Judging an event
+after them needs nothing it forgot: the version, every party's keys and node list, and
+the proposals on the current version with their votes all count, and are kept. A node
+starting from a checkpoint reads what it keeps as written under its version, as it holds
+none of their histories: each was written under that one or an earlier, counting there,
+a kept proposal is on it, and a later `since` that leaves one out is past it. A node
+that can't build a checkpoint, as it was away across a move and a remake after it, or as
+it joins, takes it only where its operator pins it ([`store.md`](store.md), Pinned
+checkpoints). What it can't check of its heads it takes on its operator's word: that
+they are after the checkpoint current at the version naming them, at which that one is
+current too; so it judges that version as every node does.
What a checkpoint loses: what counted no more before it, so that a key added back, or a
place given back, brings back nothing signed before it, and a party that voted twice on