search

ensdomains / ens

Implementations for ENS core functionality: The registry, registrars, and public resolvers.
https://ens.domains/
BSD 2-Clause "Simplified" License
1.16k stars 511 forks source link

Suggestion: Add .ly.eth, .co.eth, .co.uk.eth, .com.eth, .se.eth, etc as sub-TLD's #194

Open veqtor opened 7 years ago

veqtor commented 7 years ago

Current auctions have seen people race to register a lot of names, I believe it would be better for everyone if a graph of every possible combination of .x.eth, .xx.eth, up to .xx.xxx.xx.xx.eth names could be registered.

Sub-TLD's would greatly help in that they allow for less profitability in squatting and speculation, the options simply will become too many with the cost too high

Furthermore, ly.eth and co.eth are such good domains, that the only reasonable solution is to make them registrars themselves

Arachnid commented 7 years ago

I think this is a reasonable idea to consider in future - but first we want to get significant experience with the current configuration.

veqtor commented 7 years ago

Excellent! I just wanted to put the idea out there. Also, it would be cool if preexisting domain owners could put a ethereum.txt file in their root with an Adress that would reserve a dresses such as .com.eth for a small fee for a limited time. I know it would be hard since it'd involve oraclize queries but

manosamy commented 7 years ago

There are 1500+ DNS TLDs, and some of those TLD.eth names are already taken. Good example is .domains. Official ENS registrar DAPP is hosted at ens.domains, but .domains.eth cant be mapped, since domains is already taken. Any mapping scheme should support all DNS TLDs current and future uniformly, may be reserve .dns.eth, and use the mapping .com.dns.eth, .domains.dns.eth?