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/checkpoints.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/checkpoints.md')
| -rw-r--r-- | docs/guides/federation/checkpoints.md | 22 |
1 files changed, 14 insertions, 8 deletions
diff --git a/docs/guides/federation/checkpoints.md b/docs/guides/federation/checkpoints.md index eb9fec2..f6340b0 100644 --- a/docs/guides/federation/checkpoints.md +++ b/docs/guides/federation/checkpoints.md @@ -22,14 +22,20 @@ isn't above the heads, which its party signs again ([After a move](#after-a-move ## Proposing one A version that only moves the store on is the current one with the next `number`, the -current version's hash as `changes`, and the heads as `checkpoint` -([`proposing-and-voting.md`](proposing-and-voting.md), -[Writing a version](proposing-and-voting.md#writing-a-version)). The heads are events -after the current checkpoint, at which the current version is current too, none in -another's history, their IDs ascending: the heads a node shows (`heads` in `GET /events`) -as late as you can, so that what was written before is in their history. Propose it -then: the client signs the proposal on the heads its node -shows then, above the ones it names, as it must be. +current version's hash as `changes`, and the heads as `checkpoint`: `propose checkpoint` +writes and proposes it, at the heads the node shows then, as late as you can, so that +what was written before is in their history: + +```sh +continuum-party --node http://tv:secret@localhost:3000 --key tv.key --record tv.record \ + propose checkpoint --yes +``` + +The heads are events after the current checkpoint, at which the current version is +current too, none in another's history, their IDs ascending; by hand, `heads` in `GET +/events` ([`proposing-and-voting.md`](proposing-and-voting.md), +[Writing a version](proposing-and-voting.md#writing-a-version)). The client signs the +proposal on the heads its node shows then, above the ones it names, as it must be. Like any version, it lapses the proposals on the version before: propose one where nothing that can still pass is proposed on the current version. |
