diff options
| author | tv <tv@krebsco.de> | 2026-11-19 14:25:53 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-19 15:28:50 +0100 |
| commit | 5d8259ce576fce47b921c0bfbd6821f255be504a (patch) | |
| tree | a9979e64cdf03816524f54568588e454baab2688 /src/document/lock.rs | |
| parent | 841897b79838f97a809356471baf2f41e186cdfa (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 'src/document/lock.rs')
0 files changed, 0 insertions, 0 deletions
