From 393fb4d70fc6bf88debc4ca13d644ea7de9602f5 Mon Sep 17 00:00:00 2001 From: tv Date: Tue, 17 Nov 2026 16:32:23 +0000 Subject: dashboard: the federation, in a swarm holding a store MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit In a swarm holding a store, the snapshot names the node's party, and the document box shows what counts as the node reads it, read every 5 s: the current version, the parties with their keys and nodes, the rules, the values at places as a tree with who writes there, the proposals on the version with where each stands, who voted what and what its version changes, and what the node refused. `document` beside `remake…` shows the document underneath. Where the node votes for its party by itself, a proposal that can still pass has a vote of each kind, cast through the node on a second click. The page writes no values: a party signs its writes with its key. --- docs/guides/federation/proposing-and-voting.md | 3 +++ 1 file changed, 3 insertions(+) (limited to 'docs/guides/federation/proposing-and-voting.md') 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 -- cgit v1.3.1