summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/guides/federation/getting-started.md14
-rw-r--r--docs/guides/federation/proposing-and-voting.md5
2 files changed, 12 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
```
diff --git a/docs/guides/federation/proposing-and-voting.md b/docs/guides/federation/proposing-and-voting.md
index 6ba2121..08fead9 100644
--- a/docs/guides/federation/proposing-and-voting.md
+++ b/docs/guides/federation/proposing-and-voting.md
@@ -47,8 +47,13 @@ is none: it can't pass, and a party's client backs none.
```sh
continuum-party --node http://tv:secret@localhost:3000 --key tv.key --record tv.record \
propose next.json
+# c41e… taken
+# proposal 8d02…
```
+With `--yes`, the client votes `true` on it too, as `vote 8d02… yes` does (Voting,
+below): a party whose node votes for it by itself votes through that node instead.
+
The client proposes only a version changing the current one, as a version must (its
`number`, `changes`, and each `since`), and says why it doesn't otherwise. The proposal
is on the current version, and its hash is the version's: the node shows it under that