diff options
| author | tv <tv@krebsco.de> | 2026-11-19 21:36:52 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-19 22:38:55 +0100 |
| commit | 5aa649bcb366ed6863732dac68ce081bacdbe4a8 (patch) | |
| tree | 4ab5498bb23cc0f0c30c804efbb5b5321c6c0f14 /docs/guides/federation | |
| parent | 237c79efc5d25f438d024522fd89ea7fc600cbd1 (diff) | |
continuum-party status: IDs and hashes whole
Now that `status` gives each thing a line of its own, there's no line to
keep short: the store's ID, its checkpoint's and the version's hash are
written whole, as node IDs and proposals' hashes were already; so are the
proposals' hashes in what a vote's guard says. Keys still go by their
fingerprints.
Diffstat (limited to 'docs/guides/federation')
| -rw-r--r-- | docs/guides/federation/watching.md | 18 |
1 files changed, 10 insertions, 8 deletions
diff --git a/docs/guides/federation/watching.md b/docs/guides/federation/watching.md index 7b71bf4..8105286 100644 --- a/docs/guides/federation/watching.md +++ b/docs/guides/federation/watching.md @@ -12,10 +12,10 @@ version, the party's keys and nodes, the node's stop, the proposals on the curre the versions the node refused of its own, and what the party signs again after a move: ``` -store 6d1e8a0c4f2b… - checkpoint 6d1e8a0c4f2b… +store 6d1e8a0c4f2b9d77… + checkpoint 6d1e8a0c4f2b9d77… 3 heads, 120 events taken after the checkpoint -version 3 (a7c2e81b9d04…) +version 3 (a7c2e81b9d0453f6…) federation 1, the base revision 3 parties, 2 passing a change: lass @@ -28,15 +28,17 @@ tv ssh-ed25519 SHA256:pX4c… (--key) ssh-ed25519 SHA256:r82M… nodes: - continuum:5be1… (alpha) - continuum:77d0… + continuum:5be1a3c09f2e4d6b… (alpha) + continuum:77d0c2e4f6a8b0c2… the node: lass's 1 proposal on version 3 (show says more): - 8d02…: can still pass, 1 more `true` passing it (2 of 3); true: tv; false: nobody + 8d02f1e3a5c7b9d0…: can still pass, 1 more `true` passing it (2 of 3); true: tv; false: nobody ``` -Each node goes by the name it gave itself (`--alias`), where it did: `names` of each -party in `GET /events/counts`. +IDs and hashes are cut short here; the client writes them whole, the shortest prefix +naming a proposal in bold on a terminal, and keys by their fingerprints. Each node goes +by the name it gave itself (`--alias`), where it did: `names` of each party in `GET +/events/counts`; one that gave itself none goes by its ID alone. * **A version the node refused** (`own` in `GET /events/refused` not empty): keys voted twice, and nodes may be apart. Act on it at once |
