From cb3ccc5c6107cc4fd96c4d7b184cc9b811857db1 Mon Sep 17 00:00:00 2001 From: tv Date: Sun, 15 Nov 2026 18:54:56 +0000 Subject: access: a new swarm's policy where it starts from content `--bootstrap-policy` records the policy in the genesis change, "no change of it from before the policy". With `--genesis --remake`, the content is a change of its own before the one recording the users and the policy. access.md says so, and that a change built on the content beside that one is refused as from the time before a strict policy. --- docs/access.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/access.md b/docs/access.md index c4ce295..ee48b8d 100644 --- a/docs/access.md +++ b/docs/access.md @@ -54,7 +54,9 @@ may do nothing until added (the genesis node warns of those of its `--htpasswd`) log in by key and sign values from the start, and with `--bootstrap-policy '{"version": 1, "values": "signed"}'` the policy (Values signed by their users, below) in the same change: the swarm is strict from its start, and no -change of it is from before the policy. +change of it is from before the policy. Started from content (`--genesis --remake`), +the content is a change of its own just before that one; a change built on it beside +that one is refused as from the time before a strict policy (below). Without it, the swarm has no registry: its users are all alike (A swarm without a registry, below), until someone gives it one. `--protocol-writers` counts in both: without a registry, as who may write protocol data; with one, to set it right -- cgit v1.3.1