aboutsummaryrefslogtreecommitdiffstats
path: root/docs/guides/federation/upgrades.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-19 01:48:58 +0000
committertv <tv@krebsco.de>2026-11-19 03:19:51 +0100
commite5f8df2a78f26d5928d1c96573dae5620dba5e25 (patch)
tree80e13aa7212b05c0a50be0c428d8377cf72b5fb0 /docs/guides/federation/upgrades.md
parent295ba74159e371bb9082fcbdada5eaf78de5d1dc (diff)
docs: quiet parties, proof of voting twice, the next change keeping the number
From the red-team review of the design: * a party that never votes holds those backing a proposal short by as many votes: they can neither pass it nor back another, a compromise all others would pass among them; `federation.md` draws that out, and the promises guide says so; * a client keeps its own votes and the nays that freed it, not another party's two: where keys voted twice, whoever saw it keeps the votes naming the party before a checkpoint leaves them out; * nothing but agreement keeps a party from using a change that keeps the federation's number before every node runs it: the next such change names itself in the version, so that two thirds decide when, and a node not running it stops at that version.
Diffstat (limited to 'docs/guides/federation/upgrades.md')
-rw-r--r--docs/guides/federation/upgrades.md5
1 files changed, 4 insertions, 1 deletions
diff --git a/docs/guides/federation/upgrades.md b/docs/guides/federation/upgrades.md
index f91143f..df01b05 100644
--- a/docs/guides/federation/upgrades.md
+++ b/docs/guides/federation/upgrades.md
@@ -41,4 +41,7 @@ otherwise, keeps the number: `ecdsa-sha2-nistp256` keys beside Ed25519 ones. Rol
first, then use it: every party's operators upgrade their nodes, and only then does a
party name such a key in a version or a key set, or sign with one. A node not upgraded
refuses what uses it and reads otherwise than the others; at a version naming such a key,
-none to it, it stops, until it is upgraded.
+none to it, it stops, until it is upgraded. Nothing but agreement keeps a party from using
+it early. The next such change names itself in the version, so that two thirds decide
+when it is used: what it adds is taken only under a version naming it, and a node not
+upgraded stops at that version.