aboutsummaryrefslogtreecommitdiffstats
path: root/docs/guides/federation/getting-started.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-19 19:05:31 +0000
committertv <tv@krebsco.de>2026-11-19 20:14:32 +0100
commitd45594b6075a3aff41fec07f2071b08399d4e944 (patch)
tree0848a6a8a69a8ae9ea3f3f853d14243b537eaa9b /docs/guides/federation/getting-started.md
parent00b5378a62d29f7489075f6d747d50f07cb45caa (diff)
docs/guides/federation: led by the new commands
Getting started lets makefu in with `propose admit`, lass seeing what it votes on before it casts, and reads with `values` and `status`; the upgrades guide proposes a revision with `propose revision`, the checkpoints guide a checkpoint with `propose checkpoint`, the keys guide names keys anew with `propose keys` and writes a namespace again from `values --json`; the troubleshooting guide points at `status` and at forks by what they are for. The JSON and `next` stay where a version is written by hand.
Diffstat (limited to 'docs/guides/federation/getting-started.md')
-rw-r--r--docs/guides/federation/getting-started.md47
1 files changed, 17 insertions, 30 deletions
diff --git a/docs/guides/federation/getting-started.md b/docs/guides/federation/getting-started.md
index 6a0aec8..483a991 100644
--- a/docs/guides/federation/getting-started.md
+++ b/docs/guides/federation/getting-started.md
@@ -141,8 +141,8 @@ names them once, when it begins its record (`init --federation NAME`), and never
lass reads it on its node, with everything else that counts:
```sh
-curl -s -u lass:secret localhost:3000/events/counts | jq .values
-# {"home/tv/motd": "hello"}
+continuum-party --node http://lass:secret@localhost:3000 values
+# home/tv/motd "hello" (tv)
```
lass can't write there: its node refuses it, as every node does.
@@ -165,48 +165,35 @@ root, as it never voted:
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, 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…",
- "keys": { "tv": { "since": 0, "keys": ["ssh-ed25519 AAAA…"] },
- "lass": { "since": 0, "keys": ["ssh-ed25519 AAAA…"] },
- "makefu": { "since": 1, "keys": ["ssh-ed25519 AAAA…"] } },
- "nodes": { "tv": { "since": 0, "nodes": ["continuum:5be1…"] },
- "lass": { "since": 0, "nodes": ["continuum:9c07…"] },
- "makefu": { "since": 1, "nodes": ["continuum:e2a8…"] } },
- "rules": [ { "path": "home/{party}/**", "writer": "{party}" } ] }
-```
-
-One of them proposes it, and votes `true` on it (`--yes`); the client says the
-proposal's hash, the version's:
+One of the founders proposes the version letting makefu in, with makefu's key and node,
+and votes `true` on it (`--yes`). The client writes it from the current one, says what it
+does and asks, and 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 --yes
+ propose admit makefu --keys makefu.key.pub --nodes continuum:e2a8… --yes
+# version 1 on 0:
+# lets makefu in: 1 key (ssh-ed25519 SHA256:2kq…); 1 node (continuum:e2a8…)
+# Propose it, and vote `true` on it? [y/N] y
# c41e… taken
# proposal 8d02…
# 5a77… taken
```
-The other votes `true` too, through its own node:
+The other looks at it, and votes `true` too, through its own node, naming the proposal by
+a prefix of its hash:
```sh
continuum-party --node http://lass:secret@localhost:3000 --key lass.key \
- --record lass.record vote 8d02… yes
+ --record lass.record vote 8d02 yes
+# 8d02…: can still pass, 1 more `true` passing it (2 of 2); true: tv; false: nobody
+# proposed by tv: version 1 on 0
+# lets makefu in: 1 key (ssh-ed25519 SHA256:2kq…); 1 node (continuum:e2a8…)
+# Vote `true` on 8d02…? [y/N] y
```
Once a node holds both votes, it writes the version, and every node takes it:
-`.version.number` in `GET /events/counts` is 1. makefu's node, started with
+`continuum-party status` says version 1. makefu's node, started with
`--store-id 6d1e… --store-party makefu` and a seed, is a member now: the others sync
with it, and makefu writes in its namespace as tv did.