aboutsummaryrefslogtreecommitdiffstats
path: root/src/access/challenge.rs
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-19 14:11:39 +0000
committertv <tv@krebsco.de>2026-11-19 15:18:45 +0100
commit27b76d5748f23a879d9fc82c725a58b514020ef9 (patch)
treed0201eed80c9c4a2db3f2e6281cac51dbc126ba6 /src/access/challenge.rs
parent8347900a553a3c4c9f9d3fc4a539fd31b41b07d3 (diff)
fork: a fork's check says what its version changes, rules among it
A node holding the history up to a fork's heads said whether it builds the root, what it holds that those heads lack, and which parties' keys the fork's version gives otherwise. A founder could change the rules, or only their order, which says who writes where, and nobody joining was shown it. The check now says what the fork's version changes of the version current at those heads, a line each as a proposal's are shown (`client::changes`): `changes` in POST /events/fork, and `continuum-party check` prints them. federation.md and the forking guide say so, and that a fork's ID is compared whole: a founder trying versions can steer its first few digits.
Diffstat (limited to 'src/access/challenge.rs')
0 files changed, 0 insertions, 0 deletions