GitLab

It doesn't actually work. Blocks are stored under /blocks and have been since
2015.

Furthermore, this is just wrong. We shouldn't go digging through the datastore
to see if we happen to have the block. If we want something like this, we should
include a blockstore in the provider manager.

Handle empty keys, both when sent in RPC requests and in the local API.

* Remove deprecated events.
* Fix warning -> warn.
* Use structured logging (some places).

Previously, we'd only return the target peer if we were connected to them.
However, this makes it difficult to impossible to find peers that are mostly
disconnected from the network.

This change also changes `p` to `from` in several places as `p` is _very_
confusing. We should probably switch away from using `p` everywhere.

* feat: Expose the ProviderManager through the IpfsDht struct
* feat: expose providers prefix so that we do not have to hard code it in other places
Co-authored-by: Aarsh Shah <aarshkshah1992@gmail.com>

fixes #274

Update deps:

* Switch to multiformats/go-base32
* Regenerate protobuf decoding code

Implement striped locking for datastore puts.

This reverts commit 7e68ac3c.

2. Switch `LogKV()` to `SetTag`.
3. Use a smarter way to log errors.

fixes #177

This way, users who are actually trying to find a peer (not just nodes near a
key in the DHT) can find that peer, even if they aren't a DHT server and/or
aren't in anyone's routing table.

fixes #161

Note: this does mean that the DHT won't work with peer keys by default and that
the constructor signature changes. Given all the changes that'll come with the
libp2p refactor, I don't feel too bad about this.

Explicitly clean DHT records before storing them.

License: MIT
Signed-off-by: ForrestWeston <forrest@protocol.ai>

Try to preallocate slices up-front instead of repeatedly reallocating.