aboutsummaryrefslogtreecommitdiffstats
path: root/docs/guides/federation
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-18 12:32:13 +0000
committertv <tv@krebsco.de>2026-11-18 13:35:01 +0100
commitb0f0e1a9edb08b324df2ec5e97d15e7089349fdb (patch)
tree19446d3a9f304ded779b3a48ab4447dc96511608 /docs/guides/federation
parent13d96ce6ecd386ddd39b803ecb52a8557476f8fa (diff)
continuum-party: proposes only what a party may back
One check (`client::backable`) decides what a party's client proposes and what it votes `true` on: a version, changing the current one as a version must, whose checkpoint, where it names one, names none of the heads of the current version's checkpoint, as a version naming those again is never written. A proposal nobody may back is refused before it is signed, saying why.
Diffstat (limited to 'docs/guides/federation')
-rw-r--r--docs/guides/federation/proposing-and-voting.md9
1 files changed, 6 insertions, 3 deletions
diff --git a/docs/guides/federation/proposing-and-voting.md b/docs/guides/federation/proposing-and-voting.md
index 9ec014b..e342b5b 100644
--- a/docs/guides/federation/proposing-and-voting.md
+++ b/docs/guides/federation/proposing-and-voting.md
@@ -54,8 +54,10 @@ continuum-party --node http://tv:secret@localhost:3000 --key tv.key --record tv.
With `--yes`, the client votes `true` on it too, as `vote 8d02… yes` does (Voting,
below): a party whose node votes for it by itself votes through that node instead.
-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
+The client proposes only a version it would back: one changing the current one as a
+version must (its `number`, `changes`, and each `since`), whose checkpoint, where it names
+one, names none of the heads of the current version's checkpoint, as such a version is
+never written. It says why it doesn't propose one 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
@@ -78,7 +80,8 @@ record before it sends the vote. It casts no vote that would make its party vote
* never `true` and `false` on one proposal, nor the same vote twice;
* nothing on the version current when the record began, as a vote sent before may be
held back somewhere;
-* `true` only for a version changing the current one;
+* `true` only for a version changing the current one, whose checkpoint names none of the
+ current checkpoint's heads;
* one `true` at a time: another `true` on the same version only once the proposal the
party backed is dead. The client fetches the votes that made it so from the node, and
keeps them in the record beside the new `true`.