summaryrefslogtreecommitdiffstats
path: root/docs/guides/federation/getting-started.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-18 11:51:31 +0000
committertv <tv@krebsco.de>2026-11-18 13:07:01 +0100
commit847b0f51b20e5a7a947f56123799e6c1166aeef0 (patch)
tree131b4908cc3ed15faa8de04c17c631b0aa732d22 /docs/guides/federation/getting-started.md
parentacfbdf87dd346137b05f8b28d54068de1c77e0c2 (diff)
continuum-party propose: the proposal's hash, and --yes
`propose` says the proposal's hash, the version's, which `vote` takes; with `--yes`, it votes `true` on it too, by the record, as `vote` does.
Diffstat (limited to 'docs/guides/federation/getting-started.md')
-rw-r--r--docs/guides/federation/getting-started.md14
1 files changed, 7 insertions, 7 deletions
diff --git a/docs/guides/federation/getting-started.md b/docs/guides/federation/getting-started.md
index 6eebbd8..5dcff5b 100644
--- a/docs/guides/federation/getting-started.md
+++ b/docs/guides/federation/getting-started.md
@@ -171,20 +171,20 @@ and makefu goes in:
"rules": [ { "path": "home/{party}/**", "writer": "{party}" } ] }
```
-One of them proposes it; the node shows the proposal by its hash, the version's:
+One of them proposes it, and votes `true` on it (`--yes`); the client says the
+proposal's hash, the version's:
```sh
continuum-party --node http://tv:secret@localhost:3000 --key tv.key --record tv.record \
- propose second.json
-curl -s -u tv:secret localhost:3000/events/counts | jq '.proposals | keys'
-# ["8d02…"]
+ propose second.json --yes
+# c41e… taken
+# proposal 8d02…
+# 5a77… taken
```
-Both vote `true`, each through its own node:
+The other votes `true` too, through its own node:
```sh
-continuum-party --node http://tv:secret@localhost:3000 --key tv.key --record tv.record \
- vote 8d02… yes
continuum-party --node http://lass:secret@localhost:3000 --key lass.key \
--record lass.record vote 8d02… yes
```