subdomain-registrar
subdomain-registrar copied to clipboard
stacks-network
Subdomain registrar for the Stacks network
There are newer request libraries such as [undici](https://github.com/nodejs/undici) that are much more easy to work with when it comes to JSON parsing, request/response schema validation, status code and headers handling,...
The registrar still contains request logic that assumes the target nodes are from Blockstack v1, including [custom load balancer logic](https://github.com/stacks-network/subdomain-registrar/blob/master/src/operations.js#L306-L318) that is no longer relevant. It should be updated to...
The registrar can receive 404 status codes from the Stacks Blockchain API if a transaction ID is not found for any reason (missing from mempool, etc.). It should try again...
The registrar currently runs on node 12, which is outdated and no longer maintained. It should be upgraded to at least node 18 which is the current LTS version.
The registrar needs to update the transaction status for a large number of transactions during operation. However, it currently issues all of these calls to the Stacks Blockchain API in...
At bootup, if the registrar cannot reach an API instance at `https://stacks-node-api.stacks.co/v2/info`, it'll log an error and fail to complete startup. It will also fail to gracefully exit. ``` registrar...
This repo is currently publishing to `blockstack/subdomain-registrar` on Docker hub. We are in the process of migrating it to [`stacksnetwork/subdomain-registrar`](https://hub.docker.com/r/stacksnetwork/subdomain-registar) [`ci.yml`](https://github.com/stacks-network/subdomain-registrar/blob/master/.github/workflows/ci.yml) file needs to get modified to publish on both...
# Description It looks like the current subdomain registrar implementation does not allow users to transfer subdomains to other addresses.
Hey, it's me and @pradel . We got a grant to improve the subdomain registrar performance, which is critical for Sigle and perhaps could be reused later on for other...
example [https://registrar.stacks.co/v1/names/alexandernacho.id.stx](https://registrar.stacks.co/v1/names/alexandernacho.id.stx) shows the linked address, `{"blockchain":"stacks","status":"submitted_subdomain","last_txid":"32ad1787fcaa6a8aaf6f29ff440fab63d098374af1549b08dff6d14db59d39cf","zonefile":"$ORIGIN alexandernacho.id.stx\n$TTL 3600\n_http._tcp\tIN\tURI\t10\t1\t\"https://gaia.blockstack.org/hub/1G6DVN2rCw4cWKpTE6yVaJQHMMpJXXfMfD/profile.json\"\n\n","address":"SP2JRCS2HC0WC5D29NC683RPXDVK9F41Y7W4EQS9V","zonefile_hash":"41c8cf0cea57becec455a6449e39f33059a9aa94"}` but calling its [stacks name](https://stacks-node-api.mainnet.stacks.co/v1/addresses/stacks/SP2JRCS2HC0WC5D29NC683RPXDVK9F41Y7W4EQS9V) or [name history](https://stacks-node-api.mainnet.stacks.co/v1/names/alexandernacho.id.stx/history) can not confirm its state in the chain. Could that come from orphaned...
