From f751f411e954001c124afa1e3591d10094df15d7 Mon Sep 17 00:00:00 2001 From: tv Date: Sun, 15 Nov 2026 16:47:46 +0000 Subject: rules: nothing added to the time before a swarm turned strict A swarm turned strict by writing the policy into it kept the time before open: a change whose history lacks the policy's change is judged by the policy then, none or one that isn't strict, needs no signature there, and is taken whenever it comes, from any member. With values read by `seq`, an envelope planted at that time with the highest `seq` there is can never be followed: a ban, a user, a declaration, for good. Once a document's policy is strict, a change written under one that isn't is refused, received or held, unless it is in the history of the change that wrote the policy the document reads (`store::written_by`). A node that holds one beside that change, taken before it came, is told so by any peer that refused it (REFUSALS), judges it again, now refuses it too, and drops it with what builds on it, as for any change it took unjudged. A swarm strict from its genesis change has no such time; one whose policy isn't strict judges as before. --- docs/access.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) (limited to 'docs') diff --git a/docs/access.md b/docs/access.md index 89e74d7..b2cdb70 100644 --- a/docs/access.md +++ b/docs/access.md @@ -470,7 +470,11 @@ that isn't strict, a member may write as any user). So a swarm is best strict fr start (`--bootstrap-policy`, A new swarm, above); one already running turns strict through a remake (Turning a swarm strict, below), which keeps only what an operator looked over. Writing the strict policy into it directly trusts it as it is: look it -over first (`continuum-signed verify` on each entry). A value there that isn't an envelope +over first (`continuum-signed verify` on each entry). From then on nothing is added to +the time before: a change written under a policy that isn't strict is refused, received +or held, unless it is in the history of the change that wrote the strict policy, so a +member can't plant at that time what nobody could follow; a node that took one beside +that change drops it once a peer tells it so (Changes judged on every node, below). A value there that isn't an envelope starts its chain anew: any envelope its user once signed for that path replacing nothing (`prev` empty) can be put there again. Without the policy, signed values may be written all the same, and plain ones too. -- cgit v1.3.1