From e9b1ea18694c88abe1e31f8236f8d8beb6362be9 Mon Sep 17 00:00:00 2001 From: tv Date: Tue, 17 Nov 2026 16:11:50 +0000 Subject: continuum-party proposals: where each proposal stands, and what it changes `continuum-party proposals` lists the proposals on the current version at the node, each with whether it passed or is dead and the parties voting `true` and `false`, as `GET /events/counts` names them, and what its version changes of the current one, read from an event proposing it, its signature checked: each field whose value differs, and of `keys` and `nodes` each party's (`client::changes`). --- docs/guides/federation/proposing-and-voting.md | 11 +++++++++++ 1 file changed, 11 insertions(+) (limited to 'docs/guides') diff --git a/docs/guides/federation/proposing-and-voting.md b/docs/guides/federation/proposing-and-voting.md index 3f4aa0f..b25e9d9 100644 --- a/docs/guides/federation/proposing-and-voting.md +++ b/docs/guides/federation/proposing-and-voting.md @@ -123,6 +123,17 @@ curl -s -u tv:secret localhost:3000/events/counts | jq .proposals # "votes":["5a77…","e019…"],"yes":["tv"]}} ``` +The client shows the same, and what each proposal's version changes of the current one, +field by field and party by party: + +```sh +continuum-party --node http://tv:secret@localhost:3000 proposals +# 8d02…: dead; true: tv; false: lass +# changes: null -> "1f4c…" +# checkpoint: - -> ["4a1d…","9e30…"] +# number: 0 -> 1 +``` + `GET /events/{id}` shows a proposing event, the version it proposes in `proposal`, and a vote, signed by its party. A node lacking some votes reads a proposal as neither passed nor dead where another reads it dead; no vote takes either back. A dead proposal stays -- cgit v1.3.1