subdomain-registrar
subdomain-registrar copied to clipboard
stacks-network
Subdomain registrar for the Stacks network
The registrar uses a naive approach for getting the current nonce - which is just to call `/v2/accounts` and get the current nonce. This does not reflect any tx's in...
Rather than using a hardcoded adminPassword in the config file like : ``` adminPassword: 'NEEDS-A-PASSWORD', ``` It would be better to use an env if present: `ADMIN_PASSWORD="my-fake-password"`. This would prevent...
This would prevent both PBC and non-PBC developers from getting blocked for a lifetime based on their IP addresses, forcing them to switch to another network as they invest more...
If we want to implement #30 and other improvements, we'll need increased code coverage in our testing. We should aim to get to 90% here. Currently ~78%
The current subdomain registrar is limited by relying on sqlite -- it makes concurrency pretty hard, and things like registrations and batch processing are currently stepping on each other's toes....
Currently, our subdomain registrar only handles registration requests. It should additionally handle updating those entries. The resolver supports parsing and verifying these updates, but an endpoint needs to be added...
We should add an admin endpoint for resetting a given IP's limit count.
The protocol supports transferring subdomains to new keys, but the registrar needs to be able to accept a signed transfer request to do so.