aboutsummaryrefslogtreecommitdiffstats
path: root/docs/guides
diff options
context:
space:
mode:
Diffstat (limited to 'docs/guides')
-rw-r--r--docs/guides/federation/watching.md64
1 files changed, 42 insertions, 22 deletions
diff --git a/docs/guides/federation/watching.md b/docs/guides/federation/watching.md
index 8105286..537e42b 100644
--- a/docs/guides/federation/watching.md
+++ b/docs/guides/federation/watching.md
@@ -7,38 +7,58 @@ store, through its API and its log.
## Through the API
-`continuum-party status` says most of what follows at a glance: the store and its
-version, the party's keys and nodes, the node's stop, the proposals on the current version,
-the versions the node refused of its own, and what the party signs again after a move:
+`continuum-party status` says everything about the federation at the node but the values
+(`get`, `values`), with what needs a look in colour on a terminal:
```
store 6d1e8a0c4f2b9d77…
checkpoint 6d1e8a0c4f2b9d77…
3 heads, 120 events taken after the checkpoint
+the node
+ lass's, voting for it by itself
+ knows the base revision, revision 1 (merge-events)
version 3 (a7c2e81b9d0453f6…)
federation 1, the base revision
- 3 parties, 2 passing a change:
- lass
- makefu
- tv
-tv
- keys the version names (votes, proposals, key set, node list):
- ssh-ed25519 SHA256:J1nQ…
- keys of its key set (writes):
- ssh-ed25519 SHA256:pX4c… (--key)
- ssh-ed25519 SHA256:r82M…
- nodes:
- continuum:5be1a3c09f2e4d6b… (alpha)
- continuum:77d0c2e4f6a8b0c2…
-the node: lass's
-1 proposal on version 3 (show says more):
- 8d02f1e3a5c7b9d0…: can still pass, 1 more `true` passing it (2 of 3); true: tv; false: nobody
+ 3 parties, 2 passing a change
+parties
+ lass
+ keys the version names (votes, proposals, key set, node list):
+ ssh-ed25519 SHA256:J1nQ…
+ keys of its key set (writes): the same
+ nodes:
+ continuum:9c07e2a4b6d8f0a1… (beta)
+ this node; wire 52; revision 1 (merge-events)
+ tv
+ keys the version names (votes, proposals, key set, node list):
+ ssh-ed25519 SHA256:pX4c…
+ keys of its key set (writes):
+ ssh-ed25519 SHA256:r82M… (--key)
+ nodes:
+ continuum:5be1a3c09f2e4d6b… (alpha)
+ heard 12 s ago; wire 52; the base revision
+proposals on version 3
+ 8d02f1e3a5c7b9d0…: can still pass, 1 more `true` passing it (2 of 3)
+ true: tv; false: nobody; not yet: lass, makefu
+ proposed by tv: version 4 on 3
+ lets makefu in: 1 key (ssh-ed25519 SHA256:2kq…); 1 node (continuum:e2a8…)
+refused
+ no version event of its own
+you: tv
+ --key ssh-ed25519 SHA256:r82M…: of the key set: writes
+ record tv.record: agrees with the node
```
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.
+naming a proposal in bold, and keys by their fingerprints. It says of every party's nodes
+the names they gave themselves (`--alias`), how long ago the node heard from each, and
+what each runs (its wire versions and the newest revision it knows: the nodes to upgrade
+before a revision passes); of every proposal how it stands, who voted what and who not
+yet, and what it does, as `show` says it; and of the party it works as (its record's,
+`--party`'s, or else the node's), its `--key`, its record held against the votes the node
+shows, what `again` signs again, and what may keep votes away. What people read may change
+from release to release; `status --json` says the same as one JSON object, whose `format`
+says which: a later release raises it where the object changes otherwise than by more
+members.
* **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