Closed matthewdowney closed 2 years ago
Hi @matthewdowney. Apologies for the delayed response, we've been thinking about this a bit. I appreciate your thoughtful proposal, but the answer is "not right now" for the following reasons:
Hey Toby, I totally understand. Thanks for considering it!
Hey @tobias , no pressure here, but wanted to check if ETH's completed move to proof of stake affects this decision. Thanks!
@matthewdowney I don't know a lot about this space, but what's to stop someone creating a .eth TLD in the future which is just a "regular" domain, not an ENS domain? How would you envision handling name conflicts? Or would you add some prefix to ENS domains to separate them?
Hey good point! I mistakenly thought they had registered .eth with ICANN but I understand from this medium post that they have not, and that it's only a future goal.
Fwiw Brave browser's strategy includes rules which recognize .eth domains, and it's gaining steam as a way to point to IPFS content, but it's always possible that ICANN decides to give .eth to Ethiopia (currently .et).
Hi there,
I hope this isn't too out of place / beyond scope, but I wanted to propose a mechanism for verifying Ethereum Name Service domains for group verification in a similar manner to verification for DNS.
For example, I own the mjd.eth domain and would like to be able to use the group id
eth.mjd
.Ownership of that ENS domain can be verified by:
What do y'all think? Is granting group id based on ENS registration desirable, and if so, is this mechanism workable?