diff options
| author | tv <tv@krebsco.de> | 2026-11-16 17:11:36 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-16 18:28:29 +0100 |
| commit | 4790838255999336113f8c086ae06eea40d1444a (patch) | |
| tree | 9a0322e6c8e947f5c7134f8cab66a0338fea2845 /docs/federation.md | |
| parent | 59864edb025ccf009ef3c7b560f059c2cd2768ed (diff) | |
federation: a node follows a party's `true`, not its proposal
A node following a party backed a proposal that party proposed, but a proposal binds its
proposer to nothing: its followers were bound by their yes, and the party it followed
was free to back another. A node follows a `true` only, and one proposing a checkpoint
backs it, so that the nodes following its party back it too.
Diffstat (limited to 'docs/federation.md')
| -rw-r--r-- | docs/federation.md | 16 |
1 files changed, 9 insertions, 7 deletions
diff --git a/docs/federation.md b/docs/federation.md index b453393..f49b9c4 100644 --- a/docs/federation.md +++ b/docs/federation.md @@ -449,17 +449,19 @@ 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 proposed or backed it, and - vote `false` where that party did. 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. +* **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. * **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. A party that keeps a proposal alive nobody else backs holds back every automatic + 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. @@ -656,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 proposes, or 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 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 | | 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 | |
