aboutsummaryrefslogtreecommitdiffstats
path: root/docs/guides/federation/when-things-go-wrong.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/when-things-go-wrong.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/when-things-go-wrong.md')
-rw-r--r--docs/guides/federation/when-things-go-wrong.md7
1 files changed, 5 insertions, 2 deletions
diff --git a/docs/guides/federation/when-things-go-wrong.md b/docs/guides/federation/when-things-go-wrong.md
index 8171201..8326f72 100644
--- a/docs/guides/federation/when-things-go-wrong.md
+++ b/docs/guides/federation/when-things-go-wrong.md
@@ -12,7 +12,8 @@ Two versions changing one are written only where keys voted twice: a party's `tr
`false` on one proposal, each shown to some, or its `true` on two. Each node takes the
first it judges and refuses the other, with everything built on it, and keeps so across
restarts (`--store-file`); its log says so (`Refused an event its history takes, by what
-this node took before: kept so`), and `GET /events/refused` lists it under `own`:
+this node took before: kept so`), `continuum-party status` says so, and `GET
+/events/refused` lists it under `own`:
```sh
curl -s -u tv:secret localhost:3000/events/refused | jq .own
@@ -63,7 +64,9 @@ took after its checkpoint: a version that moved it to a checkpoint it undoes onl
taking a checkpoint its operator pins (`--store-checkpoint`).
The parties answer keys that voted twice by forking, without the party that voted twice
-or with its keys named anew ([`forking-and-following.md`](forking-and-following.md)).
+(`continuum-party fork remove lass`) or with its keys named anew (`fork keys lass
+KEY…`), at the heads of the side they keep
+([`forking-and-following.md`](forking-and-following.md)).
Tell the other parties what your node took and what it refused, and send them your
record.