aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--docs/federation.md20
1 files changed, 10 insertions, 10 deletions
diff --git a/docs/federation.md b/docs/federation.md
index f49b9c4..97f3285 100644
--- a/docs/federation.md
+++ b/docs/federation.md
@@ -451,19 +451,19 @@ 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 a `false` on
- any proposal, which can only end one, and a `true` only on a version that only moves
- to a checkpoint (Checkpoints); its operator may have it follow a `true` on any
- version, which hands that party the node's vote.
+ 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), 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.
* **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
by its own clock, by which nothing anyone judges goes. It proposes only where nothing
that can still pass is proposed on the current version, as such a version lapses what
- is. It backs what it proposes, so that the nodes following its party back it too. A
- party that keeps a proposal alive nobody else backs holds back every automatic
- checkpoint, until nays make it dead; the party a node follows votes it `false`, and
- its followers with it.
+ is, but a proposal it wouldn't back that nobody backs but its proposer: so a party
+ keeping one alive holds back no checkpoint. It backs what it proposes, so that the
+ nodes following its party back it too.
Such a node keeps to what a party's client keeps to: one yes at a time; never `true` and
`false` on one proposal, so a party has one node vote by itself, as two of its nodes
@@ -658,7 +658,7 @@ 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 a version that changes more than its checkpoint | By default the node doesn't back it; one following a `true` on any version does, as its operator chose. A `false` it follows on any proposal | 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 |
| 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 |
@@ -667,7 +667,7 @@ crafted events. *Sim*: a simulation. *Bench*: measured, not judged.
| 64 | Checkpoint heads before the current checkpoint, or at which it isn't current, or one in another's history | No version: a version event naming it is refused | unit |
| 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, or its operator votes by hand beside the node that votes for it | Voting twice: a party votes from one client, the node that votes for it where it has one, through which it votes by hand | — |
-| 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 |
+| 67 | A party keeps a proposal alive that nobody else backs, to hold back automatic checkpoints | Holds back none: a node proposes a checkpoint beside a proposal it wouldn't back that nobody backs but its proposer | 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