-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stacks gTLD Proposal #83
Comments
Would you prefer .stacks or .stx or some other shorter TLD? Previously, we've also seen interest around a .app TLD for apps. |
I think .stx would be perfect, it's short and sweet. Unfortunately, shorter TLDs are not possible unless you create a new country. The .app TLD is totally possible and I think it would be great to show that it's an app, not a feature of Stacks such as hub.stx, etc. |
Why wouldn't this functionality begin with .id and/or .id.blockstack? Starting here gives all existing users an immediate benefit. |
.id.stx would work for that. subdomains would be very easy to create and maintain |
From the FAQ
This may be a blocker though, are they still processing applications?
@dantrevino I think the problem with
|
@whoabuddy, @muneeb-ali: @dantrevino pointed out to me that .crypto is not an ICANN TLD. That means we should just use a browser extension or something along those lines until we can get support, possibly with https://unstoppabledomains.com On the topic of .id, I already tried it out with https://reger.id, and I just ended up making it my static site. |
Ok, I didnt realize .id was a country specific tld. So .id is out. |
.stx is the asset ticker symbol while .stacks is the name of the chain. The less specific choice "stacks" is better as you can have sub-domains that make sense... stx.stacks othertoken.stacks hello-world.app.stacks brad.user.stacks |
@fluidvoice I think having support for both would be ideal, if it ends up being free through unstoppable; for now, I'm building a browser extension to deal with searches under .stx and .stacks |
We can make it that .stx is the asset ticker symbol and the symbol of the chain. Then we can have token.stx, chain.stx, other-token.stx I am not sure about helloword.app.stx. helloworld.app makes more sense to me. |
What is the main appeal of .stx, is it just that it's 3 letters like Ethereum .eth or .ens domain names? helloworld.app is more likely to have name collisions and is less explicit than say helloworld.app.stx (versus eg helloworld.app.algo). |
I think what should happen is "Stacks partner apps" can receive higher prestige domains such as email.stx / email.stacks. Then, for other apps, we can do { app name }.app.stx or even just keep conventional naming processes (naming it something completely different, like Sigle) such as sigle.stx /sigle.stacks |
The shorter the better. I don't necessarily want to have a .stx name for my Stacks app, in the same way I don't want helloworld.app.usdollar or helloworld.app.oauth |
Let's start with stacks.org and create the corresponding subdomains:
|
Closing this issue due to lack of activity. If anyone is interested in continuing the discussion, feel free to comment or reopen! |
1. Overview
Blockchain domains are human-readable addresses for not as friendly blockchain addresses. There are many use cases, such as:
wallet addresses:
This would increase the user-friendliness of exchanging money/crypto. (In this situation, id is the second-level domain, stacks obviously being the top-level domain, and then the id of the person is the subdomain/third-level domain.)
Dapp links:
Gaia hubs would be extremely easy to handle:
The list continues. There are many more possibilities, such as:
2. Dapp domains
As a developer of user-related apps, I buy many domains to maintain a good look of whatever I'm building. I think what would need to happen to eliminate domain squatters is give out/allow purchasing of domains on a quarterly basis (or just some time-based system) to dapps. Dapps would need to be registered and up-to-date to ensure that high-quality domains are providing high-quality dapps. If not, the domain would be given to some other related dapp, or given as a prize for a hackathon to whoever has the best dapp in the category related to the domain (like my example, email.stacks - email.stacks would be given to whichever email-related dapp has the highest quality and the highest consistency of updating).
3. User-related domains
Another use case is user-related domains. This would provide easy access to user-related data (only for the user and for dapps that would happen to need user-related data). Some examples:
4. Articles to read for more information:
5. Cons
The cons of buying a dedicated domain are the price, the possibility of limiting creativity, and the possibility of (like I mentioned) domain squatters. Any FAQs about registering TLDs can be found here: https://newgtlds.icann.org/en/applicants/global-support/faqs/faqs-en
Disclaimer: I am not entirely sure this is completely possible, but it's worth looking into. If there's anything I missed, or any other ideas to add, put it below. Thanks!
The text was updated successfully, but these errors were encountered: