aboutsummaryrefslogtreecommitdiffstats
path: root/docs/guides/federation
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
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')
-rw-r--r--docs/guides/federation/common-changes.md4
-rw-r--r--docs/guides/federation/getting-started.md11
-rw-r--r--docs/guides/federation/proposing-and-voting.md8
3 files changed, 14 insertions, 9 deletions
diff --git a/docs/guides/federation/common-changes.md b/docs/guides/federation/common-changes.md
index 2e5861e..acbd98a 100644
--- a/docs/guides/federation/common-changes.md
+++ b/docs/guides/federation/common-changes.md
@@ -12,9 +12,7 @@ hash as `changes`, and no `checkpoint` (a version names one only to move the sto
on, and the current version's heads are behind):
```sh
-curl -s -u tv:secret localhost:3000/events/counts |
- jq '.version as $v | $v.version | .number += 1 | .changes = $v.hash | del(.checkpoint)' \
- > next.json
+continuum-party --node http://tv:secret@localhost:3000 next > next.json
```
Each recipe is a `jq` filter on that file; then propose the result, and vote.
diff --git a/docs/guides/federation/getting-started.md b/docs/guides/federation/getting-started.md
index 6f1693c..6eebbd8 100644
--- a/docs/guides/federation/getting-started.md
+++ b/docs/guides/federation/getting-started.md
@@ -150,8 +150,15 @@ continuum-party --record makefu.record init makefu --root root
```
The founders write the version letting makefu in: the next number, the hash of the
-version it changes (`.version.hash` in `GET /events/counts`), makefu's keys and node
-list named anew in it (`since` its number), and the founders' as they were:
+version it changes, makefu's keys and node list named anew in it (`since` its number),
+and the founders' as they were. `continuum-party next` gives the current version with
+the first two changed:
+
+```sh
+continuum-party --node http://tv:secret@localhost:3000 next > second.json
+```
+
+and makefu goes in:
```json
{ "federation": 1, "number": 1, "changes": "1f4c…",
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.