aboutsummaryrefslogtreecommitdiffstats
path: root/docs/guides/federation/proposing-and-voting.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-18 11:50:43 +0000
committertv <tv@krebsco.de>2026-11-18 12:59:11 +0100
commit1c0ad4202d971a3555157c2babc07999d166959d (patch)
treef413efe7f137c0d52d07a1e657688ca60a80b405 /docs/guides/federation/proposing-and-voting.md
parentaa77c10a8a20356c277e511e9c6e33c98c9b4104 (diff)
continuum-party next: the version after the current one, to change
`next` prints the current version numbered on, naming its hash as the version it changes, and without the checkpoint it names, whose heads are behind: what a party changes and proposes. The guides begin a version with it.
Diffstat (limited to 'docs/guides/federation/proposing-and-voting.md')
-rw-r--r--docs/guides/federation/proposing-and-voting.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/guides/federation/proposing-and-voting.md b/docs/guides/federation/proposing-and-voting.md
index 5330b06..7293fba 100644
--- a/docs/guides/federation/proposing-and-voting.md
+++ b/docs/guides/federation/proposing-and-voting.md
@@ -10,14 +10,14 @@ node list and its key set are its own to write, without a vote
## Writing a version
A version is the whole policy, not a change to it. Begin from the current one, as a node
-shows it ([`common-changes.md`](common-changes.md) does the first steps below in one):
+shows it, with `number` and `changes` set and its `checkpoint` left out, as below:
```sh
-curl -s -u tv:secret localhost:3000/events/counts | jq .version.version > next.json
-curl -s -u tv:secret localhost:3000/events/counts | jq -r .version.hash
+continuum-party --node http://tv:secret@localhost:3000 next > next.json
```
-Then change it:
+What each field holds, to change ([`common-changes.md`](common-changes.md) has recipes
+for the changes made most):
* **`number`**: one more than the current version's.
* **`changes`**: the current version's hash.