diff options
Diffstat (limited to 'docs/guides/federation/proposing-and-voting.md')
| -rw-r--r-- | docs/guides/federation/proposing-and-voting.md | 23 |
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 |
