aboutsummaryrefslogtreecommitdiffstats
path: root/docs/guides
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-19 20:58:40 +0000
committertv <tv@krebsco.de>2026-11-19 22:10:16 +0100
commit59cc0283117be6b4195afbe857d702e7f8ddba6e (patch)
treee16ca3aeddb1007eff6b5b289b95a9f562730199 /docs/guides
parent011560a72ca895d8b516983485cfc45c9984cd45 (diff)
continuum-party status: a key, a node, a party a line, nodes by their names
`status` said each party's keys and nodes in one line, separated by commas, nodes by their IDs alone. Now each goes on a line of its own, indented beneath its heading (party_lines): the keys the version names, which sign votes, proposals, the key set and node list; those of the key set as it counts, which sign writes, or `the same`; `--key`'s marked, and said where it is none of them; and the nodes, each with the name it gave itself (`--alias`) where it did, as the dashboard names nodes. The store and the version are a heading each too, the parties one a line. The names come from GET /events/counts, which gives each party's `names` now (by node ID, of the nodes that gave themselves one), so that a party's session, which reads no /peers, has them. Bash completion reads the parties from the new layout.
Diffstat (limited to 'docs/guides')
-rw-r--r--docs/guides/federation/watching.md29
1 files changed, 28 insertions, 1 deletions
diff --git a/docs/guides/federation/watching.md b/docs/guides/federation/watching.md
index d99d36c..7b71bf4 100644
--- a/docs/guides/federation/watching.md
+++ b/docs/guides/federation/watching.md
@@ -9,7 +9,34 @@ store, through its API and its log.
`continuum-party status` says most of what follows at a glance: the store and its
version, the party's keys and nodes, the node's stop, the proposals on the current version,
-the versions the node refused of its own, and what the party signs again after a move.
+the versions the node refused of its own, and what the party signs again after a move:
+
+```
+store 6d1e8a0c4f2b…
+ checkpoint 6d1e8a0c4f2b…
+ 3 heads, 120 events taken after the checkpoint
+version 3 (a7c2e81b9d04…)
+ federation 1, the base revision
+ 3 parties, 2 passing a change:
+ lass
+ makefu
+ tv
+tv
+ keys the version names (votes, proposals, key set, node list):
+ ssh-ed25519 SHA256:J1nQ…
+ keys of its key set (writes):
+ ssh-ed25519 SHA256:pX4c… (--key)
+ ssh-ed25519 SHA256:r82M…
+ nodes:
+ continuum:5be1… (alpha)
+ continuum:77d0…
+the node: lass's
+1 proposal on version 3 (show says more):
+ 8d02…: can still pass, 1 more `true` passing it (2 of 3); true: tv; false: nobody
+```
+
+Each node goes by the name it gave itself (`--alias`), where it did: `names` of each
+party in `GET /events/counts`.
* **A version the node refused** (`own` in `GET /events/refused` not empty): keys voted
twice, and nodes may be apart. Act on it at once