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/promises.md | 5 +++-- docs/guides/federation/upgrades.md | 5 ++++- docs/guides/federation/when-things-go-wrong.md | 4 +++- 3 files changed, 10 insertions(+), 4 deletions(-) (limited to 'docs/guides/federation') diff --git a/docs/guides/federation/promises.md b/docs/guides/federation/promises.md index 9059764..733c713 100644 --- a/docs/guides/federation/promises.md +++ b/docs/guides/federation/promises.md @@ -38,12 +38,13 @@ to whom. A party whose machine is taken over whole is the adversary from then on * **Progress**: if the parties don't cooperate, nothing passes; those who do, fork. * **Good votes**: a party may vote badly; a `true` binds it while its proposal can - pass. + pass, and only other parties' nays free it: parties that never vote hold it there. * **Delivery**: what a party's nodes withhold reaches nobody through them. * **Speed and uptime**: a party that floods the store, or keeps remakes from committing, makes nodes slow or runs them out of memory, never wrong. The others fork away from it. * **One swarm where keys voted twice**: each node keeps the version it took, and nodes - part, until their operators choose ([`when-things-go-wrong.md`](when-things-go-wrong.md)). + part, until their operators choose + ([`when-things-go-wrong.md`](when-things-go-wrong.md)). * **Writes from before a move**: what isn't above a checkpoint's heads is refused once nodes moved there; its party signs it again ([`checkpoints.md`](checkpoints.md)). * **A joining node's view**: a node joining from the root of a federation that never 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. diff --git a/docs/guides/federation/when-things-go-wrong.md b/docs/guides/federation/when-things-go-wrong.md index 7c814c2..fad11c5 100644 --- a/docs/guides/federation/when-things-go-wrong.md +++ b/docs/guides/federation/when-things-go-wrong.md @@ -38,7 +38,9 @@ continuum-party twice tv.record lass.record makefu.record That proves the party's keys signed both, not that it meant to: two of its clients, two of its nodes each voting by itself, a vote by hand beside a node voting for it, or a -stolen key look the same. Keep the records: once a checkpoint left those votes out, they +stolen key look the same. Keep the records, and the two votes naming the party, fetched +from a node while it holds them (`GET /events/{id}`): a client keeps its own votes and the +nays that freed it, not another party's, and once a checkpoint left those votes out, they show nowhere else. ## Choosing a side -- cgit v1.3.1