Vasco Santos

> Maybe somehow IPFS and/or libp2p try to reuse peer id from the past? That seems a high possibility, and is why I mention removing the repo. When you dial...

> I didn't quite follow the suggestion of removing the peers from the repo If you have problematic addresses in your node's PeerStore (addresses with wrong peerIds), this error will...

@alanshaw @dirkmc could I get your feedback on this PR? It is important to also look at the `bitswap`PR in this context. FYI, for getting this to the finish line...

Thanks @dirkmc ! I think that I addressed all your comments! Regarding persisting the time of the last provide, the first reprovide will happen once the node starts, after a...

I was waiting on [https://github.com/ipfs/js-ipfs/pull/2022](https://github.com/ipfs/js-ipfs/pull/2022) getting merged, which had a lot of useful code to integrate here without duplicating.

Having a reference to the `README` seems a cool idea!

Added this to the #655 Epic issue for `0.30`

This should be part of #744 and will be moved to `0.31`

@jacobheun let me know your thoughts on this. 🏁 are the points where we need a decision

> With this approach, how would you announce your local network addresses? Right now announce addresses are stringified multiaddrs, how would a user generate this for configuration? In the same...