aboutsummaryrefslogtreecommitdiffstats
path: root/docs/federation.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-16 04:14:00 +0000
committertv <tv@krebsco.de>2026-11-16 04:14:00 +0000
commit88536531e309d7ba2f8ebaa82431618f617347fe (patch)
tree729c6d0f41849f3ef812d059c9699bd4a752d658 /docs/federation.md
parent2377063b455aaf4b629e1bce372d55fd05c214c1 (diff)
federation: a passed version written as soon as a node holds it passed
Any member wrote a passed version; when, and which, the design didn't say: every node that sees it passed, the one that took the last vote, or one after a wait. A node writes it as soon as it holds it passed; the same version written by several is one, as a node takes a version it took written again.
Diffstat (limited to 'docs/federation.md')
-rw-r--r--docs/federation.md11
1 files changed, 6 insertions, 5 deletions
diff --git a/docs/federation.md b/docs/federation.md
index 3acde81..e83cefe 100644
--- a/docs/federation.md
+++ b/docs/federation.md
@@ -259,11 +259,12 @@ The five back nothing else on this version, and the others take X or fork. A pro
that could pass at one history and be taken back at another would let two versions be
written without anyone voting twice.
-Once a proposal passed on the current version, any member writes it at
-`_continuum/federation/versions/<hash>`, with the key sets and node lists it sets
-(Keys, Nodes); every node judges that change by its history: the proposal written there,
-on the version the text changes, its votes there, and that version current. A version
-takes effect when it is written, and judges every change in sight of it.
+Once a proposal passed on the current version, a node writes it as soon as it holds it
+passed, at `_continuum/federation/versions/<hash>`, with the key sets and node lists it
+sets (Keys, Nodes): any member may, and the same version written by several is one
+(below). Every node judges that change by its history: the proposal written there, on
+the version the text changes, its votes there, and that version current. A version takes
+effect when it is written, and judges every change in sight of it.
**A node takes a version only where it changes the version the node reads**, or is one
it took, written again. A change writing any other, valid at its history or not, it