aboutsummaryrefslogtreecommitdiffstats
path: root/docs/federation.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/federation.md')
-rw-r--r--docs/federation.md20
1 files changed, 14 insertions, 6 deletions
diff --git a/docs/federation.md b/docs/federation.md
index 2041d7e..f77c3c4 100644
--- a/docs/federation.md
+++ b/docs/federation.md
@@ -401,6 +401,12 @@ As the version naming the current checkpoint is among the next checkpoint's head
their history, every later version naming one names heads after those, and a node
starting from a checkpoint holds what judging them reads. A proposer names heads it has
held for a while, by its own clock, which judges nothing, so that every node holds them.
+A party's client, and a node voting by itself, back a checkpoint only where everything
+they held for a while before it was proposed is among its heads, in their history, or
+above them: a move refuses what isn't above its heads, and heads a proposer made up,
+built on little, would take back what was written since, a key set dropping a stolen key
+among it. A node shows, for a proposed checkpoint, what it holds that its heads lack, as
+for a fork (Forks). This is the voter's rule, by its own clock: nothing more is judged.
It is a version only where its proposal is above those heads, and a vote on it, or a
version event writing it, is taken only where it is above them too
([`store.md`](store.md), Events): so moving to the checkpoint refuses nothing that
@@ -419,9 +425,9 @@ What a checkpoint loses: what counted no more before it, so that a key added bac
place given back, brings back nothing signed before it, and a party that voted twice on
a version behind it shows only in the votes its clients kept; and what isn't above its
heads, which its party signs again. Few are: the heads are ones its proposer held for a
-while, nodes build on them while the vote takes its course, a client writing once a
-checkpoint is proposed builds only on what is above its heads, and a party's client
-signs again what a move refused.
+while, no voter backs heads that leave out what it held for a while, nodes build on them
+while the vote takes its course, a client writing once a checkpoint is proposed builds
+only on what is above its heads, and a party's client signs again what a move refused.
**Joining.** Once a checkpoint passed, a node joins from a checkpoint its operator pins,
not from the root ([`store.md`](store.md), Pinned checkpoints). From the root, keys a
@@ -460,9 +466,10 @@ Such a node keeps to what a party's client keeps to: one yes at a time; never `t
`false` on one proposal, so a party has one node vote by itself, as two of its nodes
each voting by itself can vote twice; none for a proposal that is no version; and, by a
rule for checkpoints, none for a version that changes more than its number, what it
-changes and its checkpoint, which it checks against the current one. Where two
-checkpoints are proposed at once, the votes split, as any do; a rule may vote `false` on
-the one it doesn't back, so that one dies and its backers are free.
+changes and its checkpoint, which it checks against the current one, nor for one whose
+heads leave out what it held for a while (Checkpoints). Where two checkpoints are
+proposed at once, the votes split, as any do; a rule may vote `false` on the one it
+doesn't back, so that one dies and its backers are free.
It signs with a key the party's version names, which the party keeps on that node, not
apart: one stolen there votes, and writes the party's key set and node list, as the
@@ -656,6 +663,7 @@ crafted events. *Sim*: a simulation. *Bench*: measured, not judged.
| 65 | After a checkpoint, a party that backed a second proposal once its first was dead, the nays that freed it withheld by those who cast them | Not named: its client keeps those nays with its `true` | unit |
| 66 | Two clients of one party back two proposals at once | Voting twice: a party votes from one client | — |
| 67 | A party keeps a proposal alive that nobody else backs, holding back automatic checkpoints | The party a node follows votes it `false`, and its followers with it, until it is dead | sim |
+| 68 | A checkpoint proposed at heads that leave out what was written since: a key set dropping a stolen key, say | Not backed: clients and nodes back a checkpoint only where what they held for a while is among its heads, in their history, or above them; a node shows what they lack | unit |
## Roads not taken