diff options
| author | tv <tv@krebsco.de> | 2026-11-19 16:25:45 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-19 17:36:31 +0100 |
| commit | 5f9469e11b09c03d58abafe1f0210b509228315c (patch) | |
| tree | f5842bc0c44e8bd50e32c86f1210544ee5d63377 /CHANGELOG.md | |
| parent | 602718835d034ef0a96c8ca29e47f06ce37008dc (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 'CHANGELOG.md')
| -rw-r--r-- | CHANGELOG.md | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/CHANGELOG.md b/CHANGELOG.md index cf54938..da25cf3 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -7,6 +7,14 @@ it from the release before ([`docs/operations.md`](docs/operations.md), ## Unreleased +* `continuum-party show` says what a proposal does, in words, before a vote: who voted + what, the parties let in or taken out, keys by fingerprint, rules added and dropped, a + checkpoint and what moving there refuses, a revision, who writes where after it. + `proposals` says each so, and `vote` says it, then asks on a terminal before it casts + ([`docs/guides/federation/proposing-and-voting.md`](docs/guides/federation/proposing-and-voting.md), + [Following a vote](docs/guides/federation/proposing-and-voting.md#following-a-vote); + [`src/federation/party.rs`](src/federation/party.rs)). + * `GET /events/counts` shows, of a proposed checkpoint, what moving there refuses of what the parties signed (`beside`), as the docs said a node shows ([`docs/guides/federation/checkpoints.md`](docs/guides/federation/checkpoints.md), |
