summaryrefslogtreecommitdiffstats
path: root/docs/guides/federation/running-a-node.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/guides/federation/running-a-node.md')
-rw-r--r--docs/guides/federation/running-a-node.md6
1 files changed, 5 insertions, 1 deletions
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