From 40ee439f36e2afb3c978d0214dd6b8319dfa9642 Mon Sep 17 00:00:00 2001 From: tv Date: Sun, 8 Nov 2026 21:51:14 +0000 Subject: remake: a strict remake of a strict swarm isn't followed Review 3, R3: 1186 kept honest nodes from proposing or voting for a strict remake of a swarm strict already, but a majority of members, each with keys of its own, could still commit one, and switch and catchup followed it without asking what kind of remake made the epoch: the registry, policy and bans of a strict swarm changing by a member majority, the honest minority following. A node now refuses to switch to such an epoch (its document's policy strict, the remake's kind strict), and catchup refuses to rejoin one whose chain of epochs holds a strict remake after the swarm was strict (as the old document is, or once a remake since made it so). access.md says so. --- docs/access.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'docs/access.md') diff --git a/docs/access.md b/docs/access.md index 46758b0..be91185 100644 --- a/docs/access.md +++ b/docs/access.md @@ -428,7 +428,8 @@ registry, the policy and the bans change only as a user who may change them sign A running swarm turns strict through a remake of its own kind, `strict`, once (a swarm strict already takes none: its registry, policy and bans change by their users' -signatures, not by a majority of members): compaction +signatures, not by a majority of members; its nodes neither vote for one nor follow one +a majority commits anyway, switching or rejoining): compaction that keeps, at the places values are signed (the registry, `_continuum/access`, the bans, the paths listed in `userSigned`), only the values an operator looked over and signed, and sets the strict policy. What was written after its base reaches the new -- cgit v1.3.1