Would it be good for Eden and EOS if we register the gTLD of EOS?
What is a gTLD? It’s the ending of a web address, the com in https://google.com or the org in http://eoscommunity.org/
I don’t know how complicated the process of registering a new top-level-domain is, but I’m sure it is possible.
You need a company and pass some hurdles and pay some fees. Not sure if it’s in the tens of thousand dollars or more than that.
This could be used for easy onboarding of users, were each account gets an automatic mini page under the {ACCOUNT_NAME}.eos with webauthn biometric keys. And if the account owner wants more capabilities, they can pay a premium to the company managing the .eos top-level-domain.
Some challenges:
How does the private for-profit-company interacts with EdenOnEOS?
What are the mechanisms for secession in case EdenOnEOS or the private company wants that?
Do we really need this? Is this just a publicity stunt? Too centralized and goes against the decentralization of blockchain?
Or is it an intermediate bridge between the (decentralized) future and the (cloud) present?
Maybe this can be realized without a gTLD? Maybe we can have many different regular domains with a standardized stack for people to install and they will be multiple gateways to the eos main net?
I was thinking of this when I realized that webauthn which leverages biometrics in a standard way requires the domain name of the site to work. It is hard wired into the standard. So if we want to make it easy to onboard new eos main net accounts without having to keep a pen and paper backup of 12 words, it will be limited to a specific website.
Perhaps this is not needed as clarion will solve the issue in a whole different way, bypassing the browser and webauthn altogether?
Even if it is criticized as just a publicity stunt, it might still be worth our while to investigate the challenges. It might evolve to an income source for EdenOnEOS