aboutsummaryrefslogtreecommitdiffstats
path: root/docs/guides/federation
diff options
context:
space:
mode:
Diffstat (limited to 'docs/guides/federation')
-rw-r--r--docs/guides/federation/proposing-and-voting.md3
-rw-r--r--docs/guides/federation/watching.md7
2 files changed, 10 insertions, 0 deletions
diff --git a/docs/guides/federation/proposing-and-voting.md b/docs/guides/federation/proposing-and-voting.md
index b25e9d9..8c9c66f 100644
--- a/docs/guides/federation/proposing-and-voting.md
+++ b/docs/guides/federation/proposing-and-voting.md
@@ -134,6 +134,9 @@ continuum-party --node http://tv:secret@localhost:3000 proposals
# number: 0 -> 1
```
+A node's dashboard shows them so too, and where the node votes for its party by itself,
+votes through it ([`dashboard.md`](../../dashboard.md), Federation).
+
`GET /events/{id}` shows a proposing event, the version it proposes in `proposal`, and
a vote, signed by its party. A node lacking some votes reads a proposal as neither passed
nor dead where another reads it dead; no vote takes either back. A dead proposal stays
diff --git a/docs/guides/federation/watching.md b/docs/guides/federation/watching.md
index b66d5b4..c04a6a3 100644
--- a/docs/guides/federation/watching.md
+++ b/docs/guides/federation/watching.md
@@ -23,6 +23,13 @@ besides it, the node's store, through its API and its log.
checkpoint would let nodes forget; a node voting by itself proposes one at a count you
set ([`voting-by-itself.md`](voting-by-itself.md)).
+## On the dashboard
+
+A node's dashboard (`/admin/dashboard`) shows the same in its document box, read every
+5 s: the version, the parties and which of their nodes are members, the values, the
+proposals with who voted what and what each changes, and what the node refused
+([`dashboard.md`](../../dashboard.md), Federation).
+
## In the log
At warn or error: