Skip to content

Resolve .eth domain names #1315

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

Closed
danfinlay opened this issue Apr 7, 2017 · 11 comments
Closed

Resolve .eth domain names #1315

danfinlay opened this issue Apr 7, 2017 · 11 comments
Labels
area-background Issues relating to the extension background process. needs-research type-enhancement
Milestone

Comments

@danfinlay
Copy link
Contributor

danfinlay commented Apr 7, 2017

The idea of hijacking the URL bar is pretty appealing.

There's talk of adding support for this to the WebExtension API.

If this was added, we'd need to do a few things:

  • Add a static site format to ENS
  • Check when a new website .ens resolves to a static site format.
  • Redirect to that site instead.
@danfinlay danfinlay added this to the ENS Integration milestone Apr 7, 2017
@danfinlay
Copy link
Contributor Author

Worth noting that ipfs is having a similar discussion.

@ramvi
Copy link

ramvi commented May 30, 2017

How is ens-chrome-extension solving this? Worth taking a look at?

They're using a thin client instead of a third party node. Shouldn't change how URL bar is hijacked.

@danfinlay
Copy link
Contributor Author

Looks like ens-chrome-extension does this by running a light client written in GO as a local process, and allowing the extension to access that.

If MetaMask wanted to provide this, we'd probably default to whatever provider the user has configured (with Infura as a fallback), and would need to consider what resource types we were able to support.

If we had an IPFS client built in, we could resolve IPFS hosted pages. If Swarm gets exposed over libp2p or webRTC, we should be able to resolve to Swarm pages.

@cjeria cjeria removed this from the ENS Integration milestone Jan 22, 2018
@danfinlay
Copy link
Contributor Author

We may also be able to cooperate with portal.network on integrating their solution, which I believe is an infura-like hosted resolver, but could probably be pointed at a user's own custom server, too.

@danfinlay
Copy link
Contributor Author

The Gnosis team would like to see this issue's priority increase, because they have some urgent needs for it.

@danfinlay danfinlay added type-enhancement area-background Issues relating to the extension background process. needs-research labels Apr 23, 2018
@danfinlay danfinlay added this to the Sprint 05 milestone Apr 23, 2018
@Arachnid
Copy link

Please bear in mind that .eth won't be the only TLD, once we enable DNS integration. Ideally the protocol should be used to distinguish whether to resolve a standard website or some other service.

@schemata-nick
Copy link

Would be super excited for this one, especially in light of the recent DNS hack

@26000
Copy link

26000 commented Aug 8, 2018

Seems like this has been implemented in the latest version. But when i looked at Portal Network's website, it said something about its proprietary services, not a word about how to make my domain resolvable to my own IPFS website hash. Are there any docs? If not, they IMO should be added to @MetaMask/faq. I don't think we want yet another integration with a proprietary vendor-locked service, do we?

The canonical way is adding a Swarm hash as content to your ENS domain resolver, but this doesn't seem to use Swarm. Even theswarm.eth doesn't load, so...

UPD: none of Portal Network websites load for me.

@bdresser
Copy link
Contributor

bdresser commented Aug 8, 2018

@26000 some folks from Portal.network built the feature, so the splash page is sort of a shoutout. We're loading ENS data from the blockchain via Infura and IPFS content via Infura as well.

Read more on how the feature is implemented in MetaMask here: https://consensys.zendesk.com/hc/en-us/articles/360012782931.

And you can find some simple guides on how to host your page on IPFS here or here.

@26000
Copy link

26000 commented Aug 9, 2018

@bdresser

oops
You're not authorized to access this page

But the first link is what i needed, was looking for a hash converter. Thanks a lot!

@bdresser
Copy link
Contributor

bdresser commented Aug 9, 2018

re-published the support article, you should be able to access now.

closing this, released in 4.9.0!

@bdresser bdresser closed this as completed Aug 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-background Issues relating to the extension background process. needs-research type-enhancement
Projects
None yet
Development

No branches or pull requests

7 participants