aboutsummaryrefslogtreecommitdiffstats
path: root/docs/guides/federation/keys.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/guides/federation/keys.md')
-rw-r--r--docs/guides/federation/keys.md7
1 files changed, 4 insertions, 3 deletions
diff --git a/docs/guides/federation/keys.md b/docs/guides/federation/keys.md
index dcac7a2..e6bf1e0 100644
--- a/docs/guides/federation/keys.md
+++ b/docs/guides/federation/keys.md
@@ -76,8 +76,8 @@ before dropping a key, sign again with a new one what should stay:
set (the client signs on the heads its node shows). For a namespace:
```sh
- curl -s -u tv:secret localhost:3000/events/counts |
- jq -c '.values | to_entries[] | select(.key | startswith("home/tv/"))' |
+ continuum-party --node http://tv:secret@localhost:3000 values home/tv --json |
+ jq -c 'to_entries[]' |
while read -r entry; do
continuum-party --node http://tv:secret@localhost:3000 --key desk.key \
--record tv.record write "$(jq -r .key <<<"$entry")" "$(jq -c .value <<<"$entry")"
@@ -92,7 +92,8 @@ signed since replaced it and no checkpoint left it out.
## Changing the keys a version names
A party proposes a version naming its keys anew (`since` that version's number), and the
-parties vote ([`proposing-and-voting.md`](proposing-and-voting.md)). Its votes and
+parties vote ([`proposing-and-voting.md`](proposing-and-voting.md)): `continuum-party
+propose keys tv tv-new.key.pub`, by another party where tv's version keys are lost. Its votes and
proposals use the new keys from that version on; its set written before counts no more,
so it writes its set again, with the new version keys.