You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking at Kademlia DHT to see if our own peer address exists is NOT a solution, because self peerId is filtered out within the protocol level.
An alternative is to create a random ID that can be derived from the PeerId, and see if it exists in DHT. However, this should either be done with persistence (e.g. no TTL) or with TTL but in a periodic manner, nevertheless increasing the size of DHT.
A better option could be with a type of handshake method between the node and RPCs / Relay nodes so that the peer is ignored if it is already within the DHT as seen by an outsider.
No description provided.
The text was updated successfully, but these errors were encountered: