aboutsummaryrefslogtreecommitdiffstats
path: root/docs/guides/federation/designing-rules.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-19 14:25:53 +0000
committertv <tv@krebsco.de>2026-11-19 15:28:50 +0100
commit5d8259ce576fce47b921c0bfbd6821f255be504a (patch)
treea9979e64cdf03816524f54568588e454baab2688 /docs/guides/federation/designing-rules.md
parent841897b79838f97a809356471baf2f41e186cdfa (diff)
docs: how large checkpoints grow, joining before the first, counting support
What the docs left unsaid: * A checkpoint names every event that counts, 32 bytes each, and has no size limit, unlike an event; nothing bounds what a party writes where its rules let it, so every node, snapshot and fork's root holds as much as it writes. A party writing more than the others will hold is taken out by a version, or the others fork. Row 73 says so, and the rules guide. * Before the first checkpoint passed, a node joins from the root and nobody pins anything: a chain of old keys needs keys a version replaced, and a node voting by itself proposes a checkpoint after every version that changes more; until that passes, a joining node takes the first of two versions it judges, as row 63 has it. * A `true` binds; what binds nobody is said outside the votes. The voting guide shows how parties count their support first by plain writes, at a place a rule gives each (`intents/{party}/**`), read at `values` in GET /events/counts.
Diffstat (limited to 'docs/guides/federation/designing-rules.md')
-rw-r--r--docs/guides/federation/designing-rules.md6
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/guides/federation/designing-rules.md b/docs/guides/federation/designing-rules.md
index db61f62..bd577cd 100644
--- a/docs/guides/federation/designing-rules.md
+++ b/docs/guides/federation/designing-rules.md
@@ -69,6 +69,12 @@ parties' votes. A rule per shared name is a vote per name, and makes every versi
much larger: give zones and blocks by rules where the spelling allows, and leave literal
rules to what is shared.
+Nor does a rule bound how many places below it a party writes, or how large a value is
+but by an event's size (256 KiB): every node holds what counts, and every checkpoint
+names it, 32 bytes an event. A party writing more than the others will hold is taken out
+by a version, or the others fork ([`federation.md`](../../federation.md),
+[Checkpoints](../../federation.md#checkpoints)).
+
## An example: the krebs registry
The krebs users who will vote are parties, each with its hosts in its namespace