aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-16 15:41:21 +0000
committertv <tv@krebsco.de>2026-11-16 16:53:10 +0100
commit5e29e1150f5c70dfbcc1a5fdc7ad5277af19305b (patch)
tree7984213fca4ea990f963d8e1438df7f61dadd15a
parent99879cf5e1dbd2bd013ca12e3bc1409d5dc87aec (diff)
docs/federation: following a nay on any proposal
A proposal kept alive to hold back automatic checkpoints is seldom a version that only moves to one, so followers who followed only such versions stayed silent when the party they follow voted it `false`. By default a node now follows a `false` on any proposal, which can only end one, and a `true` only on a version that only moves to a checkpoint; following a `true` on any version stays its operator's choice.
-rw-r--r--docs/federation.md9
1 files changed, 5 insertions, 4 deletions
diff --git a/docs/federation.md b/docs/federation.md
index 138a46c..4cb919d 100644
--- a/docs/federation.md
+++ b/docs/federation.md
@@ -436,9 +436,10 @@ the rules are written nowhere in the swarm, and every node judges what such a no
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 the rule follows only versions that only
- move to a checkpoint (Checkpoints); its operator may have it follow on any version,
- which hands that party the node's vote.
+ 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.
* **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
@@ -656,7 +657,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 | A rule for checkpoints doesn't back it; one following on any version does, as its operator chose | 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 |
| 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 |