From 72814677f123a0396eb480246e257e27d4ac214b Mon Sep 17 00:00:00 2001 From: tv Date: Mon, 16 Nov 2026 17:15:22 +0000 Subject: federation: an event whose history holds two versions changing one is refused No node takes such a history, as each refuses one of the two, but judging, and a model reading every history anew, are given it, and must say the same of it: it is refused, as no version is current there. --- docs/federation.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'docs/federation.md') diff --git a/docs/federation.md b/docs/federation.md index 3bcbcd6..5dbc804 100644 --- a/docs/federation.md +++ b/docs/federation.md @@ -312,7 +312,8 @@ chain the node took. it at a history from before the version that followed: some party among them backed that one too (two shares of two thirds share a party). Each node keeps the version it took and refuses the other, so nodes holding the same events still read the same - policy; the sides are apart, and a node that lagged behind, or joins, may be shown + policy, and an event whose history holds both is refused, as no version is current + there; the sides are apart, and a node that lagged behind, or joins, may be shown either first. The parties answer by forking, without the party that voted twice, or with its keys named anew (Forks). * **A party that voted twice shows** in the votes alone, both signed with keys their -- cgit v1.3.1