From 5611555bd31e5b05bcee6c6e4450adeffd2e820b Mon Sep 17 00:00:00 2001 From: tv Date: Thu, 19 Nov 2026 03:54:54 +0000 Subject: held: a node merges its store's heads beyond what an event may name Past 64 heads, no event is above them all, and what is written builds on the earliest 64 alone: where nobody writes, heads apart stay apart, and a checkpoint naming them is never written. Under a revision with merge events, a node its party lists signs merge events with its node key where its store holds more heads than an event may name, each on as many as it may, the earliest taken first, until no more are left (`Holding::merge`). The worker does so a random wait after the heads first were too many, as it puts again what the document lacks, so that of the members few do at once. `federation.md` says so under Nodes, and the guides say what a node writes by itself and what its log says. --- docs/federation.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'docs/federation.md') diff --git a/docs/federation.md b/docs/federation.md index ecc3f21..d10a220 100644 --- a/docs/federation.md +++ b/docs/federation.md @@ -595,7 +595,10 @@ puts whatever events it is given, its party's and others' alike: what counts is an event, not which node put it. So a party without nodes of its own writes through any node that takes its events. Under a revision with merge events, a node its party lists signs merge events with its own key ([Events](#events)): they count for nothing, and only -gather what they build on into the history of what builds on them. +gather what they build on into the history of what builds on them. It does so by itself +where its store holds more heads than an event may name, a random wait after it first +did, so that of the members few do at once: each on as many as an event may name, the +earliest taken first, until no more are left. ### Forks -- cgit v1.3.1