aboutsummaryrefslogtreecommitdiffstats
path: root/docs/guides/federation/proposing-and-voting.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/guides/federation/proposing-and-voting.md')
-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 0f303ea..2bf0dee 100644
--- a/docs/guides/federation/proposing-and-voting.md
+++ b/docs/guides/federation/proposing-and-voting.md
@@ -65,7 +65,8 @@ version must (its `number`, `changes`, and each `since`), whose checkpoint, wher
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.
+hash (`proposals` in `GET /events/counts`), with the events proposing it that a vote
+may build on: of a checkpoint, those above its heads.
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: the
client checks that before it signs, and records nothing otherwise.