Revamp the Subdomain Registrar

[rafaelcr]

The following is a list of issues that must be tackled in order to bring the subdomain registrar to a much better operating condition than it has today.

The current version has been increasingly harder to deploy and maintain given that it is a 6-year old project that has not been worked on for a while, and which assumes the Stacks chain works differently than it does today. Once these issues are resolved, a new release should be published and an effort should be made to get other interested parties, applications and users in the Stacks ecosystem to contribute to its development.

Items are not necessarily in order of priority or severity.

• https://github.com/stacks-network/subdomain-registrar/issues/103
• https://github.com/stacks-network/subdomain-registrar/issues/104
• https://github.com/stacks-network/subdomain-registrar/issues/102
• https://github.com/stacks-network/subdomain-registrar/issues/101
• https://github.com/stacks-network/subdomain-registrar/issues/100
• https://github.com/stacks-network/subdomain-registrar/issues/90
• https://github.com/stacks-network/subdomain-registrar/issues/77
• https://github.com/stacks-network/subdomain-registrar/issues/64
• https://github.com/stacks-network/subdomain-registrar/issues/49
• https://github.com/stacks-network/subdomain-registrar/issues/30

[wileyj]

@MarvinJanssen @friedger @hstove is this something either of you can take a look into?