From acfbdf87dd346137b05f8b28d54068de1c77e0c2 Mon Sep 17 00:00:00 2001 From: tv Date: Wed, 18 Nov 2026 11:51:01 +0000 Subject: continuum-party propose: only a version changing the current one The client proposes a version only where it changes the current one as a version must (its number, the hash it names, each `since`), and says why it doesn't otherwise: no other can pass. --- docs/guides/federation/proposing-and-voting.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'docs/guides') diff --git a/docs/guides/federation/proposing-and-voting.md b/docs/guides/federation/proposing-and-voting.md index 7293fba..6ba2121 100644 --- a/docs/guides/federation/proposing-and-voting.md +++ b/docs/guides/federation/proposing-and-voting.md @@ -49,8 +49,10 @@ continuum-party --node http://tv:secret@localhost:3000 --key tv.key --record tv. propose next.json ``` -The proposal is on the current version, and its hash is the version's: the node shows it -under that hash (`proposals` in `GET /events/counts`), with the events proposing it. +The client proposes only a version changing the current one, as a version must (its +`number`, `changes`, and each `since`), and says why it doesn't otherwise. The proposal +is on the current version, and its hash is the version's: the node shows it under that +hash (`proposals` in `GET /events/counts`), with the events proposing it. Several parties proposing the same version make one proposal. The key a party proposes and votes with is one the current version names for it, not one of its key set. -- cgit v1.3.1