diff options
| author | tv <tv@krebsco.de> | 2026-11-19 19:05:31 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-19 20:14:32 +0100 |
| commit | d45594b6075a3aff41fec07f2071b08399d4e944 (patch) | |
| tree | 0848a6a8a69a8ae9ea3f3f853d14243b537eaa9b /docs/guides/federation/upgrades.md | |
| parent | 00b5378a62d29f7489075f6d747d50f07cb45caa (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/upgrades.md')
| -rw-r--r-- | docs/guides/federation/upgrades.md | 16 |
1 files changed, 9 insertions, 7 deletions
diff --git a/docs/guides/federation/upgrades.md b/docs/guides/federation/upgrades.md index 9025164..cb82382 100644 --- a/docs/guides/federation/upgrades.md +++ b/docs/guides/federation/upgrades.md @@ -83,19 +83,21 @@ adds is refused everywhere until a version names it. A node says nothing on a build from before it said this, or where this node didn't hear from it since it started: each says it with each handshake. -2. **Propose.** A party begins the next version following it, by the feature it adds; - `next` says so where its node knows a later revision than the current version's: +2. **Propose.** A party proposes the next version following it, by the feature it adds + (`next` says which, where its node knows a later revision than the current + version's): ```sh - continuum-party --node http://tv:secret@localhost:3000 next --revision merge-events \ - > next.json continuum-party --node http://tv:secret@localhost:3000 --key tv.key \ - --record tv.record propose next.json + --record tv.record propose revision merge-events + # version 5 on 4: + # moves to revision 1 (merge-events) + # Propose it? [y/N] y # proposal 5e81… ``` - Where nodes the parties list aren't known to know the revision, `next` warns, and - names them. It may already hold what the revision adds to a version: a version is read + Where nodes the parties list aren't known to know the revision, the client names + them before it asks. It may already hold what the revision adds to a version: a version is read by the revision it names. Its proposal and the votes on it are judged under the current version, and what the revision adds to events counts from the version after. |
