Hello everybody.
I have couple of questions that might be important for (not only crypto)world acceptance.
I know about some special browsers, that work with .eth names. But if there some modules or plugins for standard browsers (like Google Chrome) to work with .eth?
What we, as a community, can do, for standard browsers improvements, so, that they(browsers) would be able to work with .eth in DEFAULT configuration from the box?
I believe 2) is very important for increasing .eth names value and as a consequence $ENS price.
Hi, Opera and Brave browsers can resolve .eth domains and IPFS, Arweave hashes. You can of course resolve .eth through .link by default and additionally .limo gateways without doing anything. An extension for Chrome and Firefox is in the works (I think)
Default resolution of .eth out of the box is not possible as such since .eth TLD is reserved for Ethiopia by ICANN. I heard a while ago that ENS was in talks with the Ethiopian government to relinquish their TLD and use an alternative one. Having said that, I do not know where I read this or how accurate this is. Perhaps someone who knows more will be able to elaborate.
What, Almonit Extension? No no, it’s a misunderstanding.
Almonit project stopped a year ago, and there are no plans to continue it. I control the domain almonit.eth. The link you gave is from more than a year ago. Almonit.eth was not updated since March 2021…
.et is the ccTLD for Ethiopia afaik, not .eth . I think it’s more about the fact that adding resolution of a new TLD usually involves passing a formal ICANN application. I guess browsers, developers and companies are somewhat obliged to obey. Feel free to correct me if I’m wrong though.
Beacon is a web browser for iOS that resolves .eth with DNS using EIP-1185. It’s the first DANE-compatible browser so you can even set up secure https for a .eth domain, without the need to trust a third-party CA.
You can download it and try http://humbly.eth, which resolves using DNS.
We will launch versions for MacOS and Windows, Android soon.
I work for ENS and have discussed this exact question with people from ICANN. Here’s my understanding:
Yes, .ETH is reserved by ICANN on DNS. They reserved all 3 letter country codes years ago (and yes, .ETH is for Ethiopia), but haven’t actually given them to the countries (which already have 2 letter country code TLDs), so .ETH is not used by anyone. My current understanding is that they don’t plan on giving them to the countries, but also don’t necessarily have plans to make them available as gTLDs. If ICANN ever did make .ETH available for registration as a gTLD, ENS may try to get it as a defensive move to prevent name collisions. But we’ll see what happens if it’s ever made available.
