aboutsummaryrefslogtreecommitdiffstats
path: root/docs/federation-tests.md
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/federation-tests.md
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/federation-tests.md')
-rw-r--r--docs/federation-tests.md5
1 files changed, 3 insertions, 2 deletions
diff --git a/docs/federation-tests.md b/docs/federation-tests.md
index d902c36..3aa1996 100644
--- a/docs/federation-tests.md
+++ b/docs/federation-tests.md
@@ -61,8 +61,9 @@ to: a stage is done when its tests are.
## Properties, over generated histories
Histories are generated: a few parties (3 to 7), their keys, versions passing, honest
-writes and votes, and an adversary that signs anything its own keys or stolen ones can,
-on any dependencies, and puts out events no party signs. Each property is checked for
+writes and votes, nodes merging under a revision with merge events or not, and an
+adversary that signs anything its own keys or stolen ones can, on any dependencies, and
+puts out events no party signs. Each property is checked for
every order of every history small enough (up to some 8 events, every order that puts
each after its dependencies), and for seeded histories and orders beyond that.