Skip to content
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

.eth blockchain domain support #75

Closed
kallisti5 opened this issue Oct 27, 2020 · 7 comments
Closed

.eth blockchain domain support #75

kallisti5 opened this issue Oct 27, 2020 · 7 comments
Labels
enhancement New feature or request

Comments

@kallisti5
Copy link

Now that Agregore supports IPFS...

.eth blockchain domains can link to IPFS content.
terarocket.eth for example links to an IPFS dns-link domain.

terarocket

You manage .eth domains at ens.domains via Web3
https://app.ens.domains

@kallisti5
Copy link
Author

kallisti5 commented Oct 27, 2020

Oh.. and here are how dnslink domains work:

[kallisti5@eris Downloads]$ dig _dnslink.terarocket.io TXT
_dnslink.terarocket.io. 300 IN TXT "dnslink=/ipfs/QmbYQTWh8FYnRBhjEzso56Q9jaJQfFNpQkkkLKhEyKd9yq"

  • terarocket.io is an A record to cloudflare-ipfs.com
  • cloudflare-ipfs.com 's IPFS gateway renders /ipns/terarocket.io from the IPFS gateway
  • The IPFS gateway gets /ipns/terarocket.io looks up _dnslink.terarocket.io and renders ipfs/QmbYQTWh8FYnRBhjEzso56Q9jaJQfFNpQkkkLKhEyKd9yq

@RangerMauve
Copy link
Member

I think the dns-link stuff should work already with the IPNS PUBLISH method.

I'm down for a PR for .eth domains.

Etherium integration at a protocol handler level would also be cool. 😁

@RangerMauve
Copy link
Member

Would also be down to get ens support into hyper:// URLs.

@KyGost
Copy link
Member

KyGost commented Nov 6, 2020

I think ENS would be really cool.

Any other distributed DNS options?

Not the biggest fan of Ethereum but I guess it's better than Bitcoin at least :-p

@KyGost
Copy link
Member

KyGost commented Nov 6, 2020

I had a play with getting ENS working but couldn't get it working, likely doing something silly.

const Web3 = require('web3')
const ENS = require('ethereum-ens')
const provider = new Web3.providers.HttpProvider()
const ens = new ENS(provider)
ens.resolver('resolver.eth').addr()
  .then(console.log)
  .catch(console.error)

@KyGost KyGost mentioned this issue Nov 8, 2020
@KyGost KyGost added the enhancement New feature or request label Nov 8, 2020
@RangerMauve
Copy link
Member

RangerMauve commented Nov 16, 2020

Had a call with Brently from ENS, seems like this could be useful. For hyper:// support we'd likely need to submit a PR to the content-hash repo in order to support it. Though maybe we could store it as a regular multicodec value.

I was thinking of talking to the Etherium Foundation folks to see if we could get a small grant to get it integrated as well as add docs for how to use it.

Could also be part of ens:// support as a protocol. 🤔

@RangerMauve
Copy link
Member

Gonna close this for now in favor of #77

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants