DHT requests before bootstrap. about go-libp2p-daemon HOT 8 CLOSED

This is a little tricky, there is no well-defined event that says "bootstrap complete".
Perhaps when enough peers have connected?

from go-libp2p-daemon.

as a workaround, the application can poll until enough connections have been created (just a few would be enough) using LIST_PEERS.

from go-libp2p-daemon.

So i can call LIST_PEERS to wait for N connections and if there some, then i can call for PROVIDE?

from go-libp2p-daemon.

The problem here comes from the fact that the DHT table is empty on start, and there's a delay before starting the periodic DHT bootstrap process.

An easy (and possibly correct) fix is to seed the routing table with the bootstrap peers. This is what go-ethereum does (just as a data point). So any queries coming performed between the startup and the first round of bootstrapping would use the bootstrap peers.

from go-libp2p-daemon.

@cheatfate I've reviewed some code and I wanted to ask you: are you using the bootstrap option when starting the daemon? This option explicitly connects to IPFS bootstrap peers (or the nodes you provide it) on startup, and then triggers periodic DHT Bootstrap. However, it is true that the control socket is opened before this happens.

from go-libp2p-daemon.

Yes i'm using -b flag, because otherwise DHT is always empty.

from go-libp2p-daemon.

Please file an issue against the DHT for this.

from go-libp2p-daemon.

The main solution here is calling LIST PEERS to wait for the number of connected peers you desire before calling PROVIDE or FIND_PROVIDERS. There's work in parallel to make bootstrapping faster, but that's tracked separately.

from go-libp2p-daemon.