aboutsummaryrefslogtreecommitdiffstats
path: root/docs/guides/federation/watching.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-17 16:10:34 +0000
committertv <tv@krebsco.de>2026-11-17 17:14:22 +0100
commit1ed4ccdb0cd3a9407b6101b1bc595df2a451a18d (patch)
treed75459a0844e3be3d9f646af66fe0ab60586b526 /docs/guides/federation/watching.md
parent2f78f51a4cd779e0ab989057727995f7bccf75ab (diff)
events: counts names who voted what, and whether a proposal passed or is dead
`GET /events/counts` gives each proposal on the current version the parties voting `true` and `false` (`yes`, `no`), whether it passed and whether it is dead (`passed`, `dead`), as the node reads its votes (`State::tally`, which the fold judges by too), so that reading where a vote stands takes no fetch of every vote. A party's client still decides its votes by the votes it checks itself.
Diffstat (limited to 'docs/guides/federation/watching.md')
-rw-r--r--docs/guides/federation/watching.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/guides/federation/watching.md b/docs/guides/federation/watching.md
index e83408f..b66d5b4 100644
--- a/docs/guides/federation/watching.md
+++ b/docs/guides/federation/watching.md
@@ -13,7 +13,8 @@ besides it, the node's store, through its API and its log.
read its store ([`when-things-go-wrong.md`](when-things-go-wrong.md), A node doing less
than it should).
* **Proposals on the current version** (`proposals` in `GET /events/counts`): each with
- the votes on it; the party's record says what it voted.
+ who voted what, and whether it passed or is dead; the party's record says what it
+ voted.
* **The version** (`.version.number` in `GET /events/counts`): a change nobody expected
is worth a look at what passed and who voted for it.
* **The members** (`members` in `GET /events/counts`): a node of your party missing