aboutsummaryrefslogtreecommitdiffstats
path: root/docs/federation.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/federation.md')
-rw-r--r--docs/federation.md16
1 files changed, 12 insertions, 4 deletions
diff --git a/docs/federation.md b/docs/federation.md
index 2cdd4d9..23522e6 100644
--- a/docs/federation.md
+++ b/docs/federation.md
@@ -296,7 +296,10 @@ A party **votes** on a proposal by a `vote` event, naming the version the propos
votes never takes back a pass or a death.
* **One yes at a time.** A party's `true` is taken only if, at its history, every other
proposal on that version it voted `true` for is dead. So a party backs one proposal,
- and is free again when that one can't pass any more.
+ and is free again when that one can't pass any more. Its next `true` builds on the
+ nays that freed it, as its first may be in the history of the proposal it backs next,
+ proposed while the first was alive, and they not; but for a checkpoint
+ ([Checkpoints](#checkpoints)).
So a yes binds its party while its proposal can pass. Of nine parties, five back X, two
prefer Y and two never vote: X needs one more and can't die, as that takes four nays.
@@ -479,11 +482,15 @@ more is judged. It is a version only where its proposal is above those heads, an
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](store.md#events)): so moving to the
checkpoint refuses nothing that decided it. A party's client, and a node voting by itself,
-vote on the events proposing what they vote on that are above those heads, as a node shows
+vote on an event proposing what they vote on that is above those heads, as a node shows
them, and a node proposes a checkpoint on its heads: so their votes are above those heads
wherever the proposal is. One proposing it again beside them they don't build on, as a
vote on it would be beside them too. 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
+until the move refuses it. Nor does a vote on a checkpoint build on the nays that freed
+its party: named, one in the history of its heads would put the vote beside them. So a
+party freed only after the heads were named, its `true` it was freed from in their
+history, backs that checkpoint not, as nodes refuse its `true`, and its client says so;
+it backs one proposed after. 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
@@ -801,10 +808,11 @@ fold, with crafted events. *Sim*: a simulation. *Bench*: measured, not judged.
| 67 | A party keeps a proposal alive that nobody else backs, or two parties of seven or more, to hold back automatic checkpoints | Holds back none past a while: a node proposes a checkpoint beside a proposal it wouldn't back that fewer than a third of the parties back, or nobody but its proposer; a new one holds back for a while, once a version for 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 |
| 69 | A key a version names, stolen, writes its party's node list at a history from before the version naming the party's keys anew, beside the list the party writes under that version, several, for the lowest ID | The party's counts: of a party's lists, those written under the latest version come first | unit |
-| 70 | A checkpoint's version proposed again, by an event beside its heads | Voters back it all the same, as a proposal lapses with the move, and vote on the events proposing it above its heads, as a node shows them; a version event on votes beside them is refused | unit |
+| 70 | A checkpoint's version proposed again, by an event beside its heads | Voters back it all the same, as a proposal lapses with the move, and vote on an event proposing it above its heads, as a node shows them; a version event on votes beside them is refused | unit |
| 71 | Merge events under the base revision, signed by a node its party doesn't list, by a party's key, or spelled otherwise | Refused, or none: a merge event is taken only under a revision with merge events, signed by a node its party's node list names, its `merge` `true`; it counts for nothing | unit |
| 72 | A version, or a fork's, admitting a party named as a segment of places others write, or changing the rules or their order, so that who writes those places moves, rules unchanged in the first case | Taken, as any version two thirds pass, or any fork: a party's client names each place holding a value whose writer a proposal changes before it is voted on, and a fork's check does for the fork's version | unit |
| 73 | A party writes a great many places, so that every node holds them, and every checkpoint, snapshot and fork's root names them | Taken where its rules let it write: nothing bounds what a party writes but the rules' places and an event's size; the others take it out by a version, or fork | — |
+| 74 | A party's second `true`, on a proposal made at a history holding its first, which nays ended later | Taken: a vote builds on the nays that freed its party, as well as on its proposal, so that the first is dead at its history; on a checkpoint only where those nays are in the history of its heads, and else the party backs the next | unit |
## Roads not taken