From 417552ecfcaa2cc74471c973fb170ff86df33d44 Mon Sep 17 00:00:00 2001
From: zzz <zzz@i2pmail.org>
Date: Fri, 10 May 2024 15:20:14 -0400
Subject: [PATCH] add note on exploration responses

---
 i2p2www/spec/i2np.rst | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/i2p2www/spec/i2np.rst b/i2p2www/spec/i2np.rst
index 6fa14b93..732e14a1 100644
--- a/i2p2www/spec/i2np.rst
+++ b/i2p2www/spec/i2np.rst
@@ -1201,6 +1201,14 @@ Notes
   For replies to regular lookups, this facilitates discovery of new floodfills
   and "backwards" searching (further-from-the-key) for robustness.
 
+* The key for an exploration lookup is usually generated randomly.
+  Therefore, the response's non-floodfill peer_hashes may be selected using an
+  optimized algorithm, such as providing peers that are close to the key but not
+  necessarily the closest in the entire local network database, to avoid an
+  inefficient sort or search of the entire local database.
+  Other strategies such as caching may also be appropriate.
+  This is implementation-dependent.
+	
 * Typical number of hashes returned: 3
 
 * Recommended maximum number of hashes to return: 16
-- 
GitLab