As a developer I struggle to sometimes register domains, especially in the crypto environment, to promote my fancy new dApp. It would be so much easier if there was a dApp/subdomain index on a (sub)TLD domain and matching dapps below that.
Description
Feature
Current Behavior
Crypto->FIAT->Registry->Domain
Expected Behavior
Crypto->(Registry OR directly ON THE BLOCKCHAIN!)->Domain
Definition of Done
[ ] Have a domain / TLD
[ ] Ability to apply for a subdomain
[ ] Ability to link subdomain to eth address (liability)
[ ] Ability to purchase or trade subdomains
[ ] Ability to allow redirection to definable address (or via intermediate layer like cloudflare)
Additional Information
This can be archived in 2 ways:
Have a (g)eth instance, write a contract "DomainContract" that has a TLD or domain as constructor parameter, a register method for registering a owner of a subdomain, a update method to update the A/AAAA/MX domain entry for registered subdomain, and corresponding events to react on the backend side. (event-oriented, possibility to extend with: fee (one time), or recurring fee (like monthly, yearly, etc.), and reserve for transfer (owner_old->owner_new))
Create a standard bounty contract instance, have it fulfill by the buyer, upon fulfilling handle all the domain related stuff on the backend.
I'd prefer the Domain Contract variant, as we would have a way of complete freedom of what to create with this and have a public consensis on the blockchain itself about the domain, owner, contract, and all other things considered.
We may even implement it as non-fungable token, which would automatically allow it to be tradeable via OpenSea etc.
User Story & Why Is this Needed
As a developer I struggle to sometimes register domains, especially in the crypto environment, to promote my fancy new dApp. It would be so much easier if there was a dApp/subdomain index on a (sub)TLD domain and matching dapps below that.
Description
Feature
Current Behavior
Crypto->FIAT->Registry->Domain
Expected Behavior
Crypto->(Registry OR directly ON THE BLOCKCHAIN!)->Domain
Definition of Done
Additional Information
This can be archived in 2 ways:
I'd prefer the Domain Contract variant, as we would have a way of complete freedom of what to create with this and have a public consensis on the blockchain itself about the domain, owner, contract, and all other things considered. We may even implement it as non-fungable token, which would automatically allow it to be tradeable via OpenSea etc.
Grand example:
Let me know about that idea, i'm really kind of thrilled about that.