aboutsummaryrefslogtreecommitdiffstats
path: root/docs/guides/federation
diff options
context:
space:
mode:
Diffstat (limited to 'docs/guides/federation')
-rw-r--r--docs/guides/federation/README.md3
-rw-r--r--docs/guides/federation/designing-rules.md6
-rw-r--r--docs/guides/federation/proposing-and-voting.md29
3 files changed, 37 insertions, 1 deletions
diff --git a/docs/guides/federation/README.md b/docs/guides/federation/README.md
index 4c5b33b..104a04c 100644
--- a/docs/guides/federation/README.md
+++ b/docs/guides/federation/README.md
@@ -11,7 +11,8 @@ by them, in its words.
* [`writing-and-reading.md`](writing-and-reading.md): places, values, what counts, why
a write is refused, and signing again after a move.
* [`proposing-and-voting.md`](proposing-and-voting.md): writing a version, proposing it,
- voting by a record, and when a proposal passes or dies.
+ voting by a record, counting support before anyone is bound, and when a proposal
+ passes or dies.
* [`keys.md`](keys.md): the keys a version names and those of a key set, changing them,
and a stolen key.
* [`checkpoints.md`](checkpoints.md): what a checkpoint does, proposing and backing one,
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
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`