From 30e1dcb98908557908ee1f79411b6dd35bff4824 Mon Sep 17 00:00:00 2001 From: Johnathan Corgan Date: Sat, 25 Jul 2026 01:56:10 +0000 Subject: [PATCH] Name this branch's third reader of the address-to-link map The doc comment merged up from the maintenance line lists the map's live readers, and on this branch there is one more: the anonymous-beacon dial dedup in poll_transport_discovery, which has no counterpart there. It reads the map with an address supplied by transport discovery, and the shared-media dial paths resolve before registering, so it compares a key written in the same form it reads and is not exposed to the mismatch the comment warns about. --- src/node/mod.rs | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/src/node/mod.rs b/src/node/mod.rs index 454a08c..20d30c3 100644 --- a/src/node/mod.rs +++ b/src/node/mod.rs @@ -307,8 +307,9 @@ struct PendingConnect { /// link. It is **not** a packet-dispatch path, despite what this comment used /// to say: `find_link_by_addr` has no callers outside its own tests, and /// encrypted frames are dispatched by session index. Its live readers are the -/// `should_admit_msg1` fast path and the duplicate-inbound-handshake check in -/// `handle_msg1`. +/// `should_admit_msg1` fast path, the duplicate-inbound-handshake check in +/// `handle_msg1`, and the anonymous-beacon dial dedup in +/// `poll_transport_discovery`. /// /// **Do not key a peer-identity question on it.** The address form is not /// canonical: an outbound dial registers the literal configured string, which