aboutsummaryrefslogtreecommitdiffstats
path: root/docs/guides
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-19 16:15:42 +0000
committertv <tv@krebsco.de>2026-11-19 17:36:10 +0100
commit9d3350f996ddba2a8e4636dd3705d9bd1c7aa4fb (patch)
treeeda545027a286d7f5359e4e1f55140ff82e31d30 /docs/guides
parent866c6a402e65f9102e63cebdf5a50c0a3f526260 (diff)
continuum-party: hashes named by their prefixes, the shortest marked
The guides wrote `vote 8d02… yes`, and the client took a whole hash only. It takes a proposal's hash by a prefix of four digits or more that no other proposal on the current version starts with (`client::named`), and says which proposals a prefix names where it names several; a whole hash is itself, as before. Heads given to `fork` are named so too, among the heads the node shows. Four digits at least, so that a prefix read a moment ago doesn't come to name a proposal made since, as one or two soon would. Where it shows a proposal's hash (`proposals`, `propose`), the client marks the shortest prefix that names it, in bold, on a terminal unless NO_COLOR is set; elsewhere the hash is printed as it was.
Diffstat (limited to 'docs/guides')
-rw-r--r--docs/guides/federation/proposing-and-voting.md8
1 files changed, 7 insertions, 1 deletions
diff --git a/docs/guides/federation/proposing-and-voting.md b/docs/guides/federation/proposing-and-voting.md
index e91806c..739552b 100644
--- a/docs/guides/federation/proposing-and-voting.md
+++ b/docs/guides/federation/proposing-and-voting.md
@@ -81,9 +81,15 @@ another proposal on it passed.
```sh
continuum-party --node http://tv:secret@localhost:3000 --key tv.key --record tv.record \
- vote 8d02… yes
+ vote 8d02 yes
```
+A proposal is named by its hash, or by a prefix of it, four digits or more, that no other
+proposal on the current version starts with: the client says which proposals a prefix
+names where it names several. On a terminal, it marks the shortest such prefix in bold
+wherever it shows a proposal's hash (`proposals`, `propose`). Heads given to `fork` are
+named so too, among the heads the node shows.
+
The client votes by the party's record, never by what a node shows, and writes the
record before it sends the vote. It casts no vote that would make its party vote twice: