I'm sure that this just because I'm not the target audience, so intend only the very gentlest criticism. But I literally LOLed at how completely incomprehensible this README was for me. It has really been a while since I've read a paragraph and had literally no idea what it was talking about. But here's the winner:

> A network agnostic DHT crawler and monitor. The crawler connects to DHT bootstrappers and then recursively follows all entries in their k-buckets until all peers have been visited.

Following the Wikipedia link for "DHT" yielded some clues. (Ah. Distributed hash table.) But I've still been looking at this for several minutes now and am basically just puzzled. But the graphs are pretty! Reading the word "amino" a little further down threw me off the scent for a bit. But I gather that is actually a proper noun, and we aren't really talking about proteins here.

Maybe an initial sentence that makes fewer assumptions about the reader's familiarity with the jargon would be helpful.

Unlucky naming collision with Slack’s networking tool Nebula: https://github.com/slackhq/nebula

It isn't really network-agnostic... in fact it doesn't support the (by far) largest DHT out there, the Mainline DHT that bittorrent uses.

This is just a crawler for DHTs that use IPFS's implementation, or at least smell very similar to it.

Why is BitTorrent not supported? Perhaps I'm misunderstanding this thing but it seems like application #1.

/me remembers various DHT views, traffic flows, client stats, graphs and other data decorations in Azureus. Now that's what I call a dashboard.

Can someone explain why we want to crawl and/or monitor? What is this used for?

When I think of a crawler, I think of a non-homogonous network (if that is the right term).

But with the blockchain, isn't it the case that each node has an entire copy of the blockchain, so you don't need to "crawl" it, it works more like a database.

What am I not understanding about this?

Instead of everyone crawling on their own, isn't it more efficient if everyone shared the same index somehow?