aboutsummaryrefslogtreecommitdiffstats
path: root/docs/MESHBAY_NODE_PROTOCOL.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/MESHBAY_NODE_PROTOCOL.md')
-rw-r--r--docs/MESHBAY_NODE_PROTOCOL.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/MESHBAY_NODE_PROTOCOL.md b/docs/MESHBAY_NODE_PROTOCOL.md
index 62a76ef..3ae533b 100644
--- a/docs/MESHBAY_NODE_PROTOCOL.md
+++ b/docs/MESHBAY_NODE_PROTOCOL.md
@@ -868,7 +868,7 @@ source of authority is a second thing to get wrong.
A code for someone who may have no account yet, so it names none: it is bound to the
first account that redeems it (`invite_link_create`, §10.4). What stops a stranger
holding it is not the node but the hub, which lets only the account whose verified
-address the inviter named reach the node at all (`docs/invite-links.md` §3.5). At the
+address the inviter named reach the node at all (`MESHBAY_DESIGN.md` §3.4). At the
node it is therefore a **bearer code**, and everything else about it is fixed:
* role `member`, never `operator`; a row that says otherwise is refused, not honoured;