From 5d8259ce576fce47b921c0bfbd6821f255be504a Mon Sep 17 00:00:00 2001 From: tv Date: Thu, 19 Nov 2026 14:25:53 +0000 Subject: 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. --- docs/guides/federation/proposing-and-voting.md | 29 ++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) (limited to 'docs/guides/federation/proposing-and-voting.md') diff --git a/docs/guides/federation/proposing-and-voting.md b/docs/guides/federation/proposing-and-voting.md index f052276..9b50e09 100644 --- a/docs/guides/federation/proposing-and-voting.md +++ b/docs/guides/federation/proposing-and-voting.md @@ -116,6 +116,35 @@ casts nothing on the current version, and votes again from the next one. A party never voted may begin its record from the root (`init --root`), and casts on every version. +## Counting support first + +A `true` isn't taken back, and binds while its proposal can pass. Parties that want to +know who would back a proposal before anyone is bound can say so by plain writes, which +bind nobody and count for nothing in the votes. The version gives each party a place for +it, by a rule: + +```json +{"path": "intents/{party}/**", "writer": "{party}"} +``` + +and each party writes there, by the proposal's hash, whether it would back it: + +```sh +continuum-party --node http://tv:secret@localhost:3000 --key tv.key --record tv.record \ + write intents/tv/8d02… true +``` + +Anyone reads them at `values` in `GET /events/counts`: + +```sh +curl -s -u tv:secret localhost:3000/events/counts \ + | jq '.values | with_entries(select(.key | test("^intents/[^/]+/8d02")))' +``` + +Once two thirds of the parties wrote `true`, each backs it. A party's write there is its +word, not its vote: it may write `false` later, or vote otherwise. It doesn't help with +parties that stay quiet: they write nothing either. + ## Passing and dying A proposal **passes** once at least two thirds of its version's parties voted `true` -- cgit v1.3.1