Vasco Santos

Thanks very much @indutny I was getting this error, if it helps:  I am not sure where it comes from so far

The easiest way is to install `peer-id` https://github.com/libp2p/js-peer-id#createopts and do: ```js const PeerId = require('peer-id') await PeerId.create() ``` (with the commit mentioned) It will create a key using [libp2p/js-libp2p-crypto](https://github.com/libp2p/js-libp2p-crypto) EDIT:...

I believe the problem is in `pem-jwk`, which is the dependency that we use, more precisely on: https://github.com/dannycoates/pem-jwk/blob/master/index.js#L150-L159

Bear in mind that the goal for `js-libp2p` users is to use `libp2p.contentRouting` for this, instead of using the `.dht` directly. That was the reason to go with the private...

You make a valid point here, which I also hit sometime ago when refactoring the DHT. With that in mind, we cannot use delegated routing for the time being in...

@kumavis thanks for exposing your thoughts here, this is valuable! I would like to see us decoupling the dht in the future into the `contentRouting` and `peerRouting`, so that we...

> However, we need to fill the gap of the put, get, getMany! Delegate nodes don't do this. They allow `findPeer`, `provide` and `findProviders`. The conversation here was going on...

@rysiekpl I recommend that you use the ipns over pubsub for the time being, while we work on improving the content routing and discoverability in the browser context. This example...

On a peer restart, it will try to dial previously known peers stored in the PeerStore (having a new setup will cause to have an empty peerStore). This can be...

Hey @stbrody I got some time to look into your test case. Thanks for providing it. I have a couple of questions. - What happens when you run `run-a.js`? Does...