aboutsummaryrefslogtreecommitdiffstats
path: root/docs/guides/federation/upgrades.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-19 16:25:45 +0000
committertv <tv@krebsco.de>2026-11-19 17:36:31 +0100
commit5f9469e11b09c03d58abafe1f0210b509228315c (patch)
treef5842bc0c44e8bd50e32c86f1210544ee5d63377 /docs/guides/federation/upgrades.md
parent602718835d034ef0a96c8ca29e47f06ce37008dc (diff)
continuum-party: show, a proposal in words before a vote
A party saw a proposal as its version's JSON changed field by field (`keys.makefu: - -> {"keys":[…],"since":4}`), and voted with nothing more before it. `continuum-party show PROPOSAL` now says what a party votes on, in words (`client::described`): * whether it passed or is dead, who voted what, and how many more `true` pass it; * who proposed it, and the version's number; * the parties it lets in or takes out, with their keys by fingerprint, as `ssh-keygen -l` gives them, and their nodes; the keys and node lists it names anew, with what it adds and drops; * the rules it adds and drops, each where it is among the rules, a rule moved being dropped at one place and added at another; * the checkpoint it moves the store to, and what moving there refuses of what the node took (`beside`); the revision it moves to, and the nodes not known to know it; * the places holding a value whose writer it changes, and why no client backs it, where none does. `proposals` says each proposal so. `vote`, through the node too, says it before anything is cast, then its warnings, and on a terminal asks: `y` casts, anything else casts nothing. Without a terminal, as in a script, it asks nothing.
Diffstat (limited to 'docs/guides/federation/upgrades.md')
-rw-r--r--docs/guides/federation/upgrades.md12
1 files changed, 6 insertions, 6 deletions
diff --git a/docs/guides/federation/upgrades.md b/docs/guides/federation/upgrades.md
index f6964a6..6ffde67 100644
--- a/docs/guides/federation/upgrades.md
+++ b/docs/guides/federation/upgrades.md
@@ -101,13 +101,13 @@ adds is refused everywhere until a version names it.
3. **Vote.** Each party backs it once every node of the party knows the revision:
```sh
- continuum-party --node http://tv:secret@localhost:3000 proposals
- # 5e81…: can still pass; true: tv; false: nobody
- # changes: "1f4c…" -> "8a20…"
- # number: 4 -> 5
- # revision: the base revision -> revision 1 (merge-events), 6c1d…
+ continuum-party --node http://tv:secret@localhost:3000 show 5e81
+ # 5e81…: can still pass, 2 more `true` passing it (3 of 4); true: tv; false: nobody
+ # proposed by tv: version 5 on 4
+ # moves to revision 1 (merge-events)
+ # not known to know revision 1 (merge-events): lass: continuum:9c07… said nothing: …
continuum-party --node http://tv:secret@localhost:3000 --key tv.key \
- --record tv.record vote 5e81… yes
+ --record tv.record vote 5e81 yes
```
The client backs it only where its node knows the revision, and says so otherwise. It