summaryrefslogtreecommitdiffstats
path: root/docs/federation.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/federation.md')
-rw-r--r--docs/federation.md27
1 files changed, 17 insertions, 10 deletions
diff --git a/docs/federation.md b/docs/federation.md
index ade27a9..784915a 100644
--- a/docs/federation.md
+++ b/docs/federation.md
@@ -505,14 +505,18 @@ A party may have one of its nodes vote and propose for it, by rules its operator
the rules are written nowhere in the swarm, and every node judges what such a node signs
as it judges any vote or proposal. The design has two in mind:
-* **Following**: back a proposal where a party the rule names backed it, and vote
- `false` where that party did; a proposal binds its proposer to nothing, so following
- one would bind the node where that party is free. By default it follows only on a
- version that only moves to a checkpoint ([Checkpoints](#checkpoints)), a `true` as a
- `false`; its operator may have it follow on any version, which hands that party the
- node's vote, its `false` among it: a party followed so by more than a third of the
- parties, its key kept on a node, ends every proposal, the one naming that key anew among
- them.
+* **Following**: back a proposal where a party the rule names backed it; a proposal
+ binds its proposer to nothing, so following one would bind the node where that party is
+ free. A `false` it copies not: copied, one party's `false` would free bound followers,
+ and its `true` shown to some and its `false` to the rest would pass a proposal at one
+ history and make it dead at another. By default it follows only on a version that only
+ moves to a checkpoint ([Checkpoints](#checkpoints)), and only where no proposal that
+ changes more can still pass, but one nobody backs but its proposer: such a version
+ lapses every other proposal, and the party it follows would end any it disliked by
+ passing one. Even so, the parties following one hand it their votes on checkpoints: with
+ them, it passes one at heads of its choosing, by the voters' rule (below). Its operator
+ may have it follow on any version, which hands that party the node's `true`: a party
+ followed so by two thirds of the parties, its key kept on a node, passes what it backs.
* **Proposing a checkpoint**: propose a version that only moves to a checkpoint, at
heads the node has held for a while, once conditions its operator sets are met: so
many events or bytes held beyond its checkpoint, so many versions since it, or so long
@@ -529,7 +533,10 @@ rule for checkpoints, none for a version that changes more than its number, what
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](#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. A node that stopped
+the one it doesn't back, so that one dies and its backers are free. It backs, and
+proposes, a checkpoint only once its store held its checkpoint, or ran, for a while, by
+its own clock: so the parties it follows move the store at most once that long, and a
+node just started, which holds nothing for a while yet, backs none. A node that stopped
at a version it doesn't read casts nothing, by itself or by hand, as what it reads is
behind ([Changing the federation](#changing-the-federation)).
@@ -722,7 +729,7 @@ fold, with crafted events. *Sim*: a simulation. *Bench*: measured, not judged.
| 55 | A checkpoint a node can't build, handed to it by peers, or a fork's root it can't check | Taken only where its operator pinned it, or named the fork | unit |
| 56 | Two versions changing one, naming different checkpoints | As 12: each node keeps the one it took, and moves to its checkpoint | unit |
| 57 | A key added back, or a place given back, after a checkpoint | Brings back nothing signed before the checkpoint that counted no more there | unit |
-| 58 | A party a node follows backs, or votes `false` on, a version that changes more than its checkpoint | By default the node follows neither; one following on any version does, as its operator chose | unit |
+| 58 | A party a node follows backs, or votes `false` on, a version that changes more than its checkpoint | By default the node follows neither; one following on any version backs the one, as its operator chose, and copies no `false` | unit |
| 59 | Two checkpoints proposed at once, by nodes voting by themselves | The votes split; nays from the nodes backing one make the other dead, and its backers are free | sim |
| 60 | Two nodes of one party, each voting by itself | They can vote twice, answered as any party voting twice: a party has one node vote by itself | — |
| 61 | A key a version names, kept on a node that votes by itself, stolen with it | As 23: it counts while that version is current | unit |