diff options
Diffstat (limited to 'docs/guides')
| -rw-r--r-- | docs/guides/federation/promises.md | 7 | ||||
| -rw-r--r-- | docs/guides/federation/running-a-node.md | 6 |
2 files changed, 9 insertions, 4 deletions
diff --git a/docs/guides/federation/promises.md b/docs/guides/federation/promises.md index 9a1b92f..9059764 100644 --- a/docs/guides/federation/promises.md +++ b/docs/guides/federation/promises.md @@ -47,9 +47,10 @@ to whom. A party whose machine is taken over whole is the adversary from then on * **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 - passed a checkpoint, whose seeds are all the adversary's, may be shown a chain that - old keys grew; a checkpoint or a fork's root a node takes on its operator's word is - only as good as that word. + passed a checkpoint may take a chain that old keys grew: shown both, it takes the first + of the two versions it judges and reports the other, for you to choose; shown that one + alone, by seeds that are all the adversary's, it takes it. A checkpoint or a fork's + root a node takes on its operator's word is only as good as that word. ## What it asks of you diff --git a/docs/guides/federation/running-a-node.md b/docs/guides/federation/running-a-node.md index 5d881d6..6444bbd 100644 --- a/docs/guides/federation/running-a-node.md +++ b/docs/guides/federation/running-a-node.md @@ -83,7 +83,11 @@ alone, so that a party listing many nodes can't be all of a node's neighbours. A node with an empty document joins by the store's ID (`--store-id`) through a member (`--seeds`), and holds its store once it has read the document: `GET /events` answers -then. +then. It learns of other members as it syncs, and needs none of its seeds once it has: +they may go away. Before a checkpoint passed, it reads from the root: of two versions +changing one, which keys voting twice wrote, it takes the first it judges, as any node, +and reports the other (`own` in `GET /events/refused`), for you to choose +([`when-things-go-wrong.md`](when-things-go-wrong.md)). Once the store moved to a checkpoint, a node joining starts from that checkpoint, which its operator pins by its ID (`--store-checkpoint`): ask a node you trust for it |
