When crawling the DHT I’m constantly issuing FIND_NODE RPCs. The response contains a list of peerIDs and also often the multi addresses. If the peer that returns the response is on an older version that doesn’t support, e.g., /quic-v1, the list of multi addresses won’t contain such addresses although the returned peer might actually support it.
The list I’m currently tracking with Nebula is the one I got handed by the other peer.
With this PR, I adjusted the crawler to await the Identify exchange and store the Multiaddresses that the peer actually reports to listen on.
When crawling the DHT I’m constantly issuing
FIND_NODERPCs. The response contains a list of peerIDs and also often the multi addresses. If the peer that returns the response is on an older version that doesn’t support, e.g.,/quic-v1, the list of multi addresses won’t contain such addresses although the returned peer might actually support it.The list I’m currently tracking with Nebula is the one I got handed by the other peer.
With this PR, I adjusted the crawler to await the Identify exchange and store the Multiaddresses that the peer actually reports to listen on.