From 74ec0acc437d0d72dc6099982fa182f1d2680d42 Mon Sep 17 00:00:00 2001 From: tv Date: Thu, 19 Nov 2026 15:05:55 +0000 Subject: federation.md: a checkpoint after every version by default, forks followed by k of m Two places the text lagged behind: a node voting by itself proposes a checkpoint after every version that changes more than moving to one, unless its operator says otherwise, where the text had it after so many versions as its operator sets; and Roads not taken turned down a node following a party's word on which fork it went to, while the attack table now names following where k of m parties went as not yet built: it says that a single party's word is what was turned down. --- docs/federation.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) (limited to 'docs/federation.md') diff --git a/docs/federation.md b/docs/federation.md index 83030ff..e13ff8a 100644 --- a/docs/federation.md +++ b/docs/federation.md @@ -580,10 +580,11 @@ as it judges any vote or proposal. The design has two in mind: heads the node holds, where they are no more than an event may name (a node merges them first, under a revision with merge events, [Nodes](#nodes)), once conditions its operator sets are met: so - many events or bytes held beyond its checkpoint, so many versions since it, or so long - by its own clock, by which nothing anyone judges goes. One after every version ends, - at the checkpoint, what keys voting twice could grow beside that version at a history - from before it. It proposes only where no + many events or bytes held beyond its checkpoint, so many versions since it that change + more than moving to a checkpoint (one, unless its operator says otherwise), or so long + by its own clock, by which nothing anyone judges goes. One after every such version + ends, at the checkpoint, what keys voting twice could grow beside that version at a + history from before it. It proposes only where no proposal on the current version holds it back, as such a version lapses what is: one it would back that can still pass; one that can still pass that a third of the parties back, someone but its proposer among them; or one new, held for less than a while, whose @@ -889,7 +890,8 @@ yet*: what would answer it better, which isn't built. stolen key would rewrite them. * **A place where a party says which fork it went to.** A node following it by itself would follow a stolen key into a swarm with any policy; parties say where they went as - they like. + they like. Following only where k of m parties a node names went would take more than + one key, and isn't built yet ([Attacks](#attacks), row 12). * **Merges**: a fork at heads of several stores, keeping what counts on each side. Its version names every party's keys anew, so that a party writes its key set again before anything a key of its set signed counts; and a value a party replaced on one -- cgit v1.3.1