diff options
| -rw-r--r-- | docs/federation.md | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/docs/federation.md b/docs/federation.md index 615bc05..e8eea8c 100644 --- a/docs/federation.md +++ b/docs/federation.md @@ -500,10 +500,11 @@ a version behind it shows only in the votes kept outside the store: a client kee 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 those its proposer held as it proposed, 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. +heads are those its proposer held as it proposed, and no voter backs heads that leave out +what it held for a while. What is written while the vote takes its course builds on the +heads its writer holds, a proposal or not, and so is above the checkpoint's heads unless +one of those is beside them: written as the proposer proposed, or built on old history. 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), |
