aboutsummaryrefslogtreecommitdiffstats
path: root/docs/access.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/access.md')
-rw-r--r--docs/access.md10
1 files changed, 10 insertions, 0 deletions
diff --git a/docs/access.md b/docs/access.md
index c5365b7..782724a 100644
--- a/docs/access.md
+++ b/docs/access.md
@@ -318,6 +318,16 @@ policy's own change and everything after it, as every other node does. While nei
its document nor what it receives holds a policy, it judges only that a root is the
epoch's, and nothing costs more than applying the changes.
+An epoch's root is pinned. A remake's is its epoch's ID, the hash of its snapshot. The
+first epoch's is its genesis change, which its genesis node logs (`The swarm's root`)
+and `GET /admin/epochs` shows (`root`). Every node names its root in its handshakes: a
+node whose document starts from another root of the same epoch refuses the handshake
+(another history under the swarm's ID: a forged root, or a genesis started again).
+A node joining with an empty document takes as its root only the one it was given
+(`--genesis-root`), or else the one its peers name, and none while they name different
+ones. So one peer hands a joiner another root only if it is all the joiner hears, or
+never, with `--genesis-root`.
+
What it doesn't do yet:
* **Prove the user.** A change is its node's (with signatures required, proven) and its