From 11a2fad727e0075fa0f5a41cb9ef297a9b273ee6 Mon Sep 17 00:00:00 2001 From: tv Date: Mon, 16 Nov 2026 17:15:05 +0000 Subject: federation: a node is still joining until it synced with every seed Of two versions changing one, a node still joining takes neither. Continuum's lifecycle has a node `Joining` only until its first sync, with one peer, its catch-up source: one node of the adversary's answering first showed it one chain alone, which it took, and refused the other from everyone else. For this, a node is still joining, from its start or a rejoin, until it has synced with every seed its operator named; and what isn't promised is a node joining whose seeds are all the adversary's. --- docs/federation.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) (limited to 'docs') diff --git a/docs/federation.md b/docs/federation.md index e431610..d64914c 100644 --- a/docs/federation.md +++ b/docs/federation.md @@ -77,7 +77,7 @@ Not promised: signs it again (Checkpoints); * that a node joining from the root, in a federation that never passed a checkpoint, isn't shown a chain old keys grew: of two versions changing one it takes neither, but - where its peers are all the adversary's it is shown one (Checkpoints); + where its seeds are all the adversary's it is shown one (Checkpoints); * that a checkpoint, or a fork's root, that a node takes on its operator's word is the one the others built ([`store.md`](store.md), Pinned checkpoints). @@ -282,10 +282,12 @@ refuses, with everything built on it, reports, and leaves to its operator ([`store.md`](store.md), A node's own); another node's refusal doesn't make it drop what it took. One valid at its history breaks no rule: the node reports it apart from events against the rules, and holds nothing against the node that put it. Of two that change -the one it reads, it takes the first it judges; a node still joining, as continuum's -lifecycle has it (`Joining`, until its first sync is done), takes neither, and reports, -until its operator names one. Without keys voting twice, every version written changes -the one every node reads, or is one it took, and none is refused. +the one it reads, it takes the first it judges; a node still joining takes neither, and +reports, until its operator names one. A node is still joining, for this, from its start +or a rejoin until it has synced with every seed its operator named: continuum's +lifecycle has it `Joining` only until its first sync, with one peer, which could be the +adversary's alone. Without keys voting twice, every version written changes the one +every node reads, or is one it took, and none is refused. **An operator may have its node drop what it took** after its checkpoint: a version the others refused, or any event, with everything built on it ([`store.md`](store.md), A -- cgit v1.3.1