aboutsummaryrefslogtreecommitdiffstats
path: root/packages/meshbay-node/tests/test_link_invites.py
diff options
context:
space:
mode:
Diffstat (limited to 'packages/meshbay-node/tests/test_link_invites.py')
-rw-r--r--packages/meshbay-node/tests/test_link_invites.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/packages/meshbay-node/tests/test_link_invites.py b/packages/meshbay-node/tests/test_link_invites.py
index f5081d2..10f9ca8 100644
--- a/packages/meshbay-node/tests/test_link_invites.py
+++ b/packages/meshbay-node/tests/test_link_invites.py
@@ -4,7 +4,7 @@ Invitation links: a code bound to no account until somebody redeems it.
A link is sent to someone who may not have an account yet, so its code cannot
name one. That makes it a bearer code at the node — the hub's ticket, bound to
a verified address, is what decides who can reach the node at all
-(docs/invite-links.md §3). Everything here is a way a bearer code could be made
+(docs/MESHBAY_DESIGN.md §3.4). Everything here is a way a bearer code could be made
to mean more than "one new member of this group, once", or a way an unbound row
could leak into the code paths written for bound ones. The second family is the
one to watch: `user_id = ''` must never read as "anyone" (AV1).