summaryrefslogtreecommitdiffstats
path: root/docs/guides/federation
diff options
context:
space:
mode:
Diffstat (limited to 'docs/guides/federation')
-rw-r--r--docs/guides/federation/proposing-and-voting.md30
1 files changed, 15 insertions, 15 deletions
diff --git a/docs/guides/federation/proposing-and-voting.md b/docs/guides/federation/proposing-and-voting.md
index 2bf0dee..6793271 100644
--- a/docs/guides/federation/proposing-and-voting.md
+++ b/docs/guides/federation/proposing-and-voting.md
@@ -38,13 +38,13 @@ for the changes made most):
Otherwise leave it out, though the current version names one: its heads are behind,
and a version naming them again is never written.
-Party names are 1 to 64 of `A-Z a-z 0-9 . _ @ -`; a party has up to 16 keys and 64
-nodes; a rule's path is a path as a write's is, its first segment literal and not
-`_continuum`, `**` last only, `{party}` once at most, and its writer a party of the
-version, `"{party}"` where the path holds it, or `false`. A version breaking any of that
-is none, and a party's client backs none; where two thirds pass it all the same, nodes
-stop at the version event writing it, until their operators have them drop it
-([`when-things-go-wrong.md`](when-things-go-wrong.md),
+Party names are 1 to 64 of `A-Z a-z 0-9 . _ @ -`; a version names up to 96 parties; a
+party has up to 16 keys and 64 nodes; a rule's path is a path as a write's is, its first
+segment literal and not `_continuum`, `**` last only, `{party}` once at most, and its
+writer a party of the version, `"{party}"` where the path holds it, or `false`. A version
+breaking any of that is none, and a party's client backs none; where two thirds pass it
+all the same, nodes stop at the version event writing it, until their operators have them
+drop it ([`when-things-go-wrong.md`](when-things-go-wrong.md),
[A node stopped](when-things-go-wrong.md#a-node-stopped)).
## Proposing
@@ -62,14 +62,14 @@ node instead.
The client proposes only a version it would back: one changing the current one as a
version must (its `number`, `changes`, and each `since`), whose checkpoint, where it names
-one, names none of the heads of the current version's checkpoint, as such a version is
-never written. It says why it doesn't propose one otherwise. The proposal
-is on the current version, and its hash is the version's: the node shows it under that
-hash (`proposals` in `GET /events/counts`), with the events proposing it that a vote
-may build on: of a checkpoint, those above its heads.
-Several parties proposing the same version make one proposal. The key a party proposes
-and votes with is one the current version names for it, not one of its key set: the
-client checks that before it signs, and records nothing otherwise.
+one, names no more than 64 heads and none of the heads of the current version's
+checkpoint, as such a version is never written. It says why it doesn't propose one
+otherwise. The proposal is on the current version, and its hash is the version's: the node
+shows it under that hash (`proposals` in `GET /events/counts`), with the events proposing
+it that a vote may build on: of a checkpoint, those above its heads. Several parties
+proposing the same version make one proposal. The key a party proposes and votes with is
+one the current version names for it, not one of its key set: the client checks that
+before it signs, and records nothing otherwise.
A proposal lapses, with the votes on it, once its version isn't current any more: when
another proposal on it passed.