diff options
Diffstat (limited to 'docs/federation.md')
| -rw-r--r-- | docs/federation.md | 20 |
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 |
