aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-16 11:47:37 +0000
committertv <tv@krebsco.de>2026-11-16 11:47:37 +0000
commit7ff0679c77be3e10348599d74941d7a28305311c (patch)
tree05abb5a532b51d1dd78488b3a3b0ab8a0b0c584a /docs
parent61e5c051159244ce5662c4ed79fc6189c1751bd9 (diff)
federation: "Why it holds" on a version written againfederation-2
"Why it holds" said a node takes a version only where it changes the one the node reads, where the design has it take one it took, written again, too.
Diffstat (limited to 'docs')
-rw-r--r--docs/federation.md20
1 files changed, 10 insertions, 10 deletions
diff --git a/docs/federation.md b/docs/federation.md
index 265718e..1cf0e76 100644
--- a/docs/federation.md
+++ b/docs/federation.md
@@ -615,16 +615,16 @@ it stays up, or how long nodes stay together.
before a version is behind what is written under it.
2. **The policy.** A version is written only where, at one history, two thirds of the
parties of the version it changes voted `true` for it, and a node takes it only where
- it changes the version the node reads. An honest party backs one proposal on a
- version at a time, and another only once the first is dead; its votes count as cast.
- So a proposal can't pass at one history and be dead at another unless some party's
- `true` and `false` for it are both there, and two proposals on one version pass only
- where some party backed both while neither was dead, or some party's `true` and
- `false` on one of them are both there. Without keys voting twice, at most one version
- changes a version, and every node takes it, however often it is written; keys an
- earlier version named move no node that took the version after it. With them, each
- node keeps the version it took, nodes holding the same changes still read the same
- policy, and the parties fork.
+ it changes the version the node reads, or is one it took. An honest party backs one
+ proposal on a version at a time, and another only once the first is dead; its votes
+ count as cast. So a proposal can't pass at one history and be dead at another unless
+ some party's `true` and `false` for it are both there, and two proposals on one
+ version pass only where some party backed both while neither was dead, or some
+ party's `true` and `false` on one of them are both there. Without keys voting twice,
+ at most one version changes a version, and every node takes it, however often it is
+ written; keys an earlier version named move no node that took the version after it.
+ With them, each node keeps the version it took, nodes holding the same changes still
+ read the same policy, and the parties fork.
3. **Remakes.** A node follows a remake only where it built the snapshot itself, from a
base it holds, a member there, the version it reads written there, its coordinator
listed; its peers' word never moves it. What came after, under that version, is