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
#59 Reports 4 big inefficiencies with our libp2p network. Problem number 1) is that libp2p attempts to connect to a bunch of addresses that don't exist rather than attempting to connect to the addresses in the bootstrap list that it is given.
This problem seems sporadic, but I think I have tracked it down to each libp2p node announcing these no-op local addresses to the network. The client receives these announced addresses from each node in the network and attempts to use them to connect to the node.
Nodes should not announce addresses that they can't be reached by. I believe the way to prevent this is to specify an announceFilter: libp2p/js-libp2p#769 (specifying the announce config only adds addresses, not subtracts them).
The text was updated successfully, but these errors were encountered:
#59 Reports 4 big inefficiencies with our libp2p network. Problem number 1) is that libp2p attempts to connect to a bunch of addresses that don't exist rather than attempting to connect to the addresses in the bootstrap list that it is given.
This problem seems sporadic, but I think I have tracked it down to each libp2p node announcing these no-op local addresses to the network. The client receives these announced addresses from each node in the network and attempts to use them to connect to the node.
Nodes should not announce addresses that they can't be reached by. I believe the way to prevent this is to specify an
announceFilter
: libp2p/js-libp2p#769 (specifying theannounce
config only adds addresses, not subtracts them).The text was updated successfully, but these errors were encountered: