aboutsummaryrefslogtreecommitdiffstats
path: root/docs/guides/federation/proposing-and-voting.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-19 18:52:37 +0000
committertv <tv@krebsco.de>2026-11-19 20:12:23 +0100
commitab9d79ba58562bfcd468afe8c2047a1110e34b7c (patch)
tree835ce4e444bcd11ef9d90c8f70f2c297e128cecb /docs/guides/federation/proposing-and-voting.md
parent97b9c45e5f8b7eed61dd494b977d27790a9544e2 (diff)
continuum-party: propose admit, remove, give, take, keys, nodes, checkpoint, revision
The changes made most no longer go through `next`, jq and a file: each is a subcommand of `propose`, which writes the next version changed so (Intent, intended) and proposes it. * admit PARTY --keys KEY|FILE... [--nodes NODE...]: its keys and node list named anew since the new number; a party already, or no party's name, refused. * remove PARTY: its keys, node list and the rules giving it places go. * give PATH PARTY|{party}: a rule first; one of that path before goes. * take PATH: the rule of that path goes, and where another rule may still give one of its places (overlaps), a rule giving them to nobody goes first. * keys PARTY KEY|FILE..., nodes PARTY NODE...: named anew. * checkpoint: at the heads the node shows. * revision FEATURE: as `next --revision`. Keys are authorized_keys lines, or files of them. Every proposal, a file's too, now says what its version does first (version_lines, shared with `show`) and asks on a terminal; with --yes the one question covers the vote, which then says and asks nothing more. A version changing only its number isn't proposed. --print writes the version instead, to change by hand and propose as a file.
Diffstat (limited to 'docs/guides/federation/proposing-and-voting.md')
-rw-r--r--docs/guides/federation/proposing-and-voting.md23
1 files changed, 18 insertions, 5 deletions
diff --git a/docs/guides/federation/proposing-and-voting.md b/docs/guides/federation/proposing-and-voting.md
index d8410f6..b58a926 100644
--- a/docs/guides/federation/proposing-and-voting.md
+++ b/docs/guides/federation/proposing-and-voting.md
@@ -10,8 +10,15 @@ its key set are its own to write, without a vote
## Writing a version
-A version is the whole policy, not a change to it. Begin from the current one, as a node
-shows it, with `number` and `changes` set and its `checkpoint` left out, as below:
+The changes made most have a command each, which writes the version from the current
+one and proposes it: `propose admit`, `remove`, `give`, `take`, `keys`, `nodes`,
+`checkpoint` and `revision` ([`common-changes.md`](common-changes.md)). With `--print`,
+each writes the version to standard output instead, to change further and propose as a
+file.
+
+A version is the whole policy, not a change to it. To write one by hand, begin from the
+current one, as a node shows it, with `number` and `changes` set and its `checkpoint`
+left out, as below:
```sh
continuum-party --node http://tv:secret@localhost:3000 next > next.json
@@ -55,13 +62,19 @@ drop it ([`when-things-go-wrong.md`](when-things-go-wrong.md),
```sh
continuum-party --node http://tv:secret@localhost:3000 --key tv.key --record tv.record \
propose next.json
+# version 4 on 3:
+# adds rule 1: names/r/wiki -> lass
+# Propose it? [y/N] y
# c41e… taken
# proposal 8d02…
```
-With `--yes`, the client votes `true` on it too, as `vote 8d02… yes` does
-([Voting](#voting), below): a party whose node votes for it by itself votes through that
-node instead.
+The client says what the version does to the current one, as `show` says it of a
+proposal ([Following a vote](#following-a-vote)), and asks before it signs, where its
+input and its errors are a terminal; asked nothing, as in a script, it goes on. It
+proposes nothing that changes the current version only by its number. With `--yes`, it
+votes `true` on it too, as `vote 8d02… yes` does ([Voting](#voting), below), asking once
+for both: a party whose node votes for it by itself votes through that node instead.
The client proposes only a version it would back: one changing the current one as a
version must (its `number`, `changes`, and each `since`), whose checkpoint, where it names