summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-18 11:53:35 +0000
committertv <tv@krebsco.de>2026-11-18 13:07:30 +0100
commit114739426a34654f1d296ed38040e369737775b2 (patch)
tree55fd48ae7b7f44bf8e106dd4e738c789bbeec8c8 /docs
parent4c823be0a7db145c43a8c67accfb6907b5d95361 (diff)
continuum-party: votes and proposals checked for the key a version names
A vote or a proposal is signed with a key the current version names for the party, as a key set and a node list are: the client checks it before it signs, and records nothing where the key isn't one.
Diffstat (limited to 'docs')
-rw-r--r--docs/guides/federation/proposing-and-voting.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/guides/federation/proposing-and-voting.md b/docs/guides/federation/proposing-and-voting.md
index 08fead9..9ec014b 100644
--- a/docs/guides/federation/proposing-and-voting.md
+++ b/docs/guides/federation/proposing-and-voting.md
@@ -59,7 +59,8 @@ The client proposes only a version changing the current one, as a version must (
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.
+and votes with is one the current version names for it, not one of its key set: the
+client checks that before it signs, and records nothing otherwise.
A proposal lapses, with the votes on it, once its version isn't current any more: when
another proposal on it passed.