Resolve pending names

[jcnelson]

In order to implement instantaneous sponsored name resolution, the registrar needs to be able to respond to GET /v1/names/{sponsored-name} and reply the same data that a Core node would reply.

My thinking is that we make core.blockstack.org reply with a 302 to the sponsored name registrar when it tries to (1) resolve a sponsored name that does not exist, and (2) detects that the sponsoring name (the on-chain name) has previously sent a zone file that lists a resolver endpoint.

Here's what I'm thinking for the implementation. In order to implement (2), the sponsoring name needs to send a zone file with the following resource record at some point:

_resolver IN URI 10 1 "https://sponsored-name-registrar.com/API/endpoint"

The Core node would send an HTTP 302 to the _resolver URI record. Specifically, it would choose the latest such record if there are multiple zone files with the _resolver record.

The client (e.g. blockstack.js, curl, etc.) would issue the GET /v1/names request to https://sponsored-name-registrar.com/API/endpoint in response to the HTTP 302.

I would implement the _resolver parsing and redirect logic in Core, and this program would implement GET /v1/names for sponsored names in the db. Do you think this is reasonable?

[jcnelson]

Related issue for the Core logic: stacks-network/stacks-core#750

[kantai]

I would implement the _resolver parsing and redirect logic in Core, and this program would implement GET /v1/names for sponsored names in the db. Do you think this is reasonable?

Yep -- that sounds reasonable to me. So the 302 would look like:

HTTP/1.1 302 Found
Location: ${_resolver_url}/v1/names/aaron.personal.id

?

[jcnelson]

Yeah, exactly!

[kantai]

Addressed in #8.

[kantai]

For setting the _resolver entry, I'll start a new issue.