From e5f8df2a78f26d5928d1c96573dae5620dba5e25 Mon Sep 17 00:00:00 2001 From: tv Date: Thu, 19 Nov 2026 01:48:58 +0000 Subject: 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. --- docs/guides/federation/upgrades.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'docs/guides/federation/upgrades.md') 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. -- cgit v1.3.1