From af120b87c42ca56f69bbe6f8d27c023919742430 Mon Sep 17 00:00:00 2001 From: tv Date: Sun, 15 Nov 2026 16:43:53 +0000 Subject: swarm: a new swarm's policy recorded in its genesis change A swarm strict from its start had its policy written by its first user in a later change. A change is judged by the policy at its history, so any member could always add a change whose history is from before the policy: judged by none, needing no signature, taken whenever it comes. Since signed values are read by `seq`, an envelope planted there with the highest `seq` there is can never be followed: a ban, a user, a declaration, for good. `--bootstrap-policy JSON`, with `--genesis`, records the policy in the genesis change, with the first users: then no change of the swarm is from before it. It must be a policy this node knows, and a strict one needs `--bootstrap-keys`, or nobody could sign what decides who may do what. --- src/simtest/mod.rs | 1 + 1 file changed, 1 insertion(+) (limited to 'src/simtest') diff --git a/src/simtest/mod.rs b/src/simtest/mod.rs index 8d6437a..40f2244 100644 --- a/src/simtest/mod.rs +++ b/src/simtest/mod.rs @@ -215,6 +215,7 @@ impl Sim { swarm_key: None, protocol_writers: HashSet::new(), first_users: Default::default(), + first_policy: None, // Under the identity layer, its key signs as a node's does. node_key: self.identity.then(|| Arc::new(sim_key(id))), sign_every: Default::default(), -- cgit v1.3.1