diff options
| -rw-r--r-- | docs/federation.md | 26 | ||||
| -rw-r--r-- | docs/guides/federation/promises.md | 5 | ||||
| -rw-r--r-- | docs/guides/federation/upgrades.md | 5 | ||||
| -rw-r--r-- | docs/guides/federation/when-things-go-wrong.md | 4 |
4 files changed, 30 insertions, 10 deletions
diff --git a/docs/federation.md b/docs/federation.md index ceb1064..a547026 100644 --- a/docs/federation.md +++ b/docs/federation.md @@ -297,6 +297,13 @@ The five back nothing else on this version, and the others take X or fork. A pro that could pass at one history and be taken back at another would let two versions be written without anyone voting twice. +So a party that doesn't vote counts as much as one that does: the two quiet ones hold the +five backing X, who can't back a compromise the seven others would all pass until X passes +or dies, and silence never ends. With q parties quiet, a proposal short by q votes or +fewer can neither pass nor die. A party gone quiet for good is taken out by a version +while two thirds still answer, and a party's client says when a `true` would bind its +party unless every party yet to vote votes `false`. + Once a proposal passed on the current version, a node writes it as soon as it holds it passed, by a **version** event, `{"deps": […], "version": <hash>}`, which no party signs: any node may write it, and the same version written by several is one (below). @@ -481,11 +488,14 @@ version as every node does. What a checkpoint loses: what counted no more before it, so that a key added back, or a place given back, brings back nothing signed before it, and a party that voted twice on -a version behind it shows only in the votes its clients kept; and what isn't above its -heads, which its party signs again. Few are: the heads are ones its proposer held for a -while, no voter backs heads that leave out what it held for a while, nodes build on them -while the vote takes its course, a client writing once a checkpoint is proposed builds -only on what is above its heads, and a party's client signs again what a move refused. +a version behind it shows only in the votes kept outside the store: a client keeps its +own votes and the nays that freed it, not another party's two, so where keys voted twice, +whoever saw it keeps the votes naming the party (`GET /events/{id}`) before a checkpoint +leaves them out; and what isn't above its heads, which its party signs again. Few are: the +heads are ones its proposer held for a while, no voter backs heads that leave out what it +held for a while, nodes build on them while the vote takes its course, a client writing +once a checkpoint is proposed builds only on what is above its heads, and a party's client +signs again what a move refused. **Joining.** Once a checkpoint passed, a node joins from a checkpoint its operator pins, not from the root ([`store.md`](store.md), @@ -852,7 +862,11 @@ otherwise, keeps the number: the keys of type `ecdsa-sha2-nistp256` taken beside ones are such a change. It is rolled out first and used after: every node runs a continuum that takes it before any party uses it. A node that doesn't refuses what uses it, and reads otherwise than the others until it does; at a version naming such a key, -which it doesn't read, it stops, as above. +which it doesn't read, it stops, as above. So that no party picks the moment nodes part, +the next such change names itself in the version, by a field that only a version using +it gives: a continuum that takes it takes what it adds only under a version naming it, +which two thirds pass, and a node running one that doesn't stops at that version rather +than refusing what follows. ## The registry on it diff --git a/docs/guides/federation/promises.md b/docs/guides/federation/promises.md index 9059764..733c713 100644 --- a/docs/guides/federation/promises.md +++ b/docs/guides/federation/promises.md @@ -38,12 +38,13 @@ to whom. A party whose machine is taken over whole is the adversary from then on * **Progress**: if the parties don't cooperate, nothing passes; those who do, fork. * **Good votes**: a party may vote badly; a `true` binds it while its proposal can - pass. + pass, and only other parties' nays free it: parties that never vote hold it there. * **Delivery**: what a party's nodes withhold reaches nobody through them. * **Speed and uptime**: a party that floods the store, or keeps remakes from committing, makes nodes slow or runs them out of memory, never wrong. The others fork away from it. * **One swarm where keys voted twice**: each node keeps the version it took, and nodes - part, until their operators choose ([`when-things-go-wrong.md`](when-things-go-wrong.md)). + part, until their operators choose + ([`when-things-go-wrong.md`](when-things-go-wrong.md)). * **Writes from before a move**: what isn't above a checkpoint's heads is refused once nodes moved there; its party signs it again ([`checkpoints.md`](checkpoints.md)). * **A joining node's view**: a node joining from the root of a federation that never diff --git a/docs/guides/federation/upgrades.md b/docs/guides/federation/upgrades.md index f91143f..df01b05 100644 --- a/docs/guides/federation/upgrades.md +++ b/docs/guides/federation/upgrades.md @@ -41,4 +41,7 @@ otherwise, keeps the number: `ecdsa-sha2-nistp256` keys beside Ed25519 ones. Rol first, then use it: every party's operators upgrade their nodes, and only then does a party name such a key in a version or a key set, or sign with one. A node not upgraded refuses what uses it and reads otherwise than the others; at a version naming such a key, -none to it, it stops, until it is upgraded. +none to it, it stops, until it is upgraded. Nothing but agreement keeps a party from using +it early. The next such change names itself in the version, so that two thirds decide +when it is used: what it adds is taken only under a version naming it, and a node not +upgraded stops at that version. diff --git a/docs/guides/federation/when-things-go-wrong.md b/docs/guides/federation/when-things-go-wrong.md index 7c814c2..fad11c5 100644 --- a/docs/guides/federation/when-things-go-wrong.md +++ b/docs/guides/federation/when-things-go-wrong.md @@ -38,7 +38,9 @@ continuum-party twice tv.record lass.record makefu.record That proves the party's keys signed both, not that it meant to: two of its clients, two of its nodes each voting by itself, a vote by hand beside a node voting for it, or a -stolen key look the same. Keep the records: once a checkpoint left those votes out, they +stolen key look the same. Keep the records, and the two votes naming the party, fetched +from a node while it holds them (`GET /events/{id}`): a client keeps its own votes and the +nays that freed it, not another party's, and once a checkpoint left those votes out, they show nowhere else. ## Choosing a side |
