aboutsummaryrefslogtreecommitdiffstats
path: root/docs/guides
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-19 03:52:49 +0000
committertv <tv@krebsco.de>2026-11-19 05:11:45 +0100
commit6c6f978189eafa15add0df865f713dc946dfc5cb (patch)
tree2b4c556ba96820aa6fd13c22d96cd5fe5af9e091 /docs/guides
parent54bcc0e4ee8e1e6a29e0e01369c2ba95b27abce8 (diff)
federation: merge events, the first revision
What builds on many heads merges them, but only an event a party writes: in a quiet federation, heads beside each other stay so, and past 64 no event is above them all. Revision 1 (`merge-events`) adds merge events: `{"merge": true}`, signed with a node's own key, the `key` its Ed25519 key, for the party whose node list names it. One counts for nothing, and only gathers what it builds on into the history of what builds on it. Under the base revision, signed by a node its party doesn't list, or by a party's key, it is refused; the model alike. Generated federations begin at either revision, and their nodes merge. A node voting by itself backs no version changing the revision, on any version neither: its party's operators vote on that one, once their nodes run a continuum that knows it. `federation.md` lists the revisions, says what a merge event is, and row 71 is tested (`federation_attack_71`).
Diffstat (limited to 'docs/guides')
-rw-r--r--docs/guides/federation/voting-by-itself.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/guides/federation/voting-by-itself.md b/docs/guides/federation/voting-by-itself.md
index a31595f..0390cfd 100644
--- a/docs/guides/federation/voting-by-itself.md
+++ b/docs/guides/federation/voting-by-itself.md
@@ -42,7 +42,8 @@ or `POST /admin/events/vote` with `{"proposal": "8d02…", "yes": true}`.
checkpoint lapses it. Even so, the parties following one hand
it their votes on checkpoints. With `--store-follow-any`, on any version: that hands
those parties the node's `true`. A party followed so by two thirds of the parties, with
- its key kept on a node, passes what it backs.
+ its key kept on a node, passes what it backs. On a version changing the revision it
+ follows never: vote on that one by hand ([`upgrades.md`](upgrades.md)).
* **After a move** (`--store-back-after`, ten minutes unless set): it backs, and proposes,
no checkpoint until its store held its checkpoint, or ran, that long by its own clock,
by itself or by hand: the parties it follows move the store once that long at most, and