From 28af1406d3158caffc27f29951c118abc25b85bd Mon Sep 17 00:00:00 2001
From: achingbrain <alex@achingbrain.net>
Date: Wed, 29 Dec 2021 09:49:48 +0100
Subject: [PATCH] fix: look for final peer event instead of peer response

`FINAL_PEER` means we found the peer, `PEER_RESPONSE` means a peer
responded to our query.
---
 src/dht/dht-peer-routing.js | 8 ++------
 1 file changed, 2 insertions(+), 6 deletions(-)

diff --git a/src/dht/dht-peer-routing.js b/src/dht/dht-peer-routing.js
index 61d79f924d..762abc80fa 100644
--- a/src/dht/dht-peer-routing.js
+++ b/src/dht/dht-peer-routing.js
@@ -27,12 +27,8 @@ class DHTPeerRouting {
    */
   async findPeer (peerId, options = {}) {
     for await (const event of this._dht.findPeer(peerId, options)) {
-      if (event.name === 'PEER_RESPONSE') {
-        const peer = event.closer.find(peerData => peerData.id.equals(peerId))
-
-        if (peer) {
-          return peer
-        }
+      if (event.name === 'FINAL_PEER') {
+        return event.peer
       }
     }