How to setup a DHT_MIRROR for blockstack-resolver?

Hi blockstackers,

I have some questions on blockstack-resolver and cannot find a channel dedicated to this component. So post it here.

Before starting resolver server, some environment variables have to be setup.

BLOCKSTACKD_IP and BLOCKSTACKD_PORT is about a blockstack-server.

Don’t know what is DHT_MIRROR at all. :thinking_face: Is it a specialized/tuned close-source components, or open-sourced? If it is open-sourced, is it a blockstack internal feature/sub components, or a separate project?

Blockstack resolver is being merged into blockstack-core.

The current repository was designed for the previous version of blockstack, 0.13, where profiles were only found via DHT. The DHT mirror was a local copy of all of the enteries in the DHT that the resolver could use instead of making a request on the DHT network. I’m not sure how to get it working with 0.14 - perhaps @muneeb can help you out?

The DHT_MIRROR is the discovery node for our DHT. We’re phasing out the use of DHT (Distributed Hash Table) and in v14 Blockstack Core nodes form a peer network to store the zone files (instead of hosting them on the DHT). More details here:

The code for the DHT is open-sourced.

Also, as Larry mentioned the resolver is in the process of being merged into Blockstack Core and the repository you’re working with will be removed shortly. Let’s talk about running the resolver as part of the new REST API of Blockstack Core instead (as that’s the new default way).

1 Like

Thanks @larry and @muneeb for your kind reply.

Actually, the reason I want to setup a blockstack-resolver is that I want to setup an blockstack-browser on blockstack (on regtest bitcoin).

I noticed that blockstack-browser depends on
The webapi seems have a relations with blockstack-resolver.

You have mentioned that blockstack-resolver is an companion of 0.13 version and 0.14 have “blockstack-resolver” embedded.

But still don’t know how to setup an private instance of “” using blockstack 0.14.

Still interest to do that.

The best way to do that is to wait until the new REST API for Blockstack Core is released.

Another option is to look at the temporary http api I’m using for Blockstack Explorer until the REST API is ready. You could probably modify that to provide the same api that the blockstack explorer expects.

Thanks @larry for a direction, I’ll dig the code.

1 Like