MetaMask to start using *.ipfs.dweb.link for ENS-IPFS sites? · Issue #493 · ipfs/infra · GitHub

Skip to content

Navigation Menu

Toggle navigation Sign in Product GitHub Copilot Write better code with AI Security Find and fix vulnerabilities Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes Discussions Collaborate outside of code Code Search Find more, search less Explore All features Documentation GitHub Skills Blog Solutions By company size Enterprises Small and medium teams Startups By use case DevSecOps DevOps CI/CD View all use cases By industry Healthcare Financial services Manufacturing Government View all industries View all solutions Resources Topics AI DevOps Security Software Development View all Explore Learning Pathways White papers, Ebooks, Webinars Customer Stories Partners Executive Insights Open Source GitHub Sponsors Fund open source developers The ReadME Project GitHub community articles Repositories Topics Trending Collections Enterprise Enterprise platform AI-powered developer platform Available add-ons Advanced Security Enterprise-grade security features GitHub Copilot Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support Pricing Search or jump to

Search code, repositories, users, issues, pull requests

Search syntax tips

Provide feedback

Cancel Submit feedback

Saved searches

Use saved searches to filter your results more quickly

Cancel Create saved search Sign in Sign up Reseting focus You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} This repository has been archived by the owner on Mar 25, 2022. It is now read-only. ipfs / infra Public archive Notifications You must be signed in to change notification settings Fork 41 Star 133 Code Issues 1 Pull requests 0 Actions Security Insights Additional navigation options Code Issues Pull requests Actions Security Insights

MetaMask to start using *.ipfs.dweb.link for ENS-IPFS sites? #493

Closed rekmarks opened this issue Nov 12, 2019 · 9 comments Closed

MetaMask to start using *.ipfs.dweb.link for ENS-IPFS sites? #493

rekmarks opened this issue Nov 12, 2019 · 9 comments

Comments

Copy link

rekmarks commented Nov 12, 2019 • edited Loading

Hello everyone, I have a support question.

Description

MetaMask , an Ethereum wallet/dapp browser, plans to start resolving ENS-IPFS/EthDNS sites using the *.ipfs.dweb.link gateway, as described in this PR . We're trying to get a hold of the proprietors of the gateway to ensure that it can handle the increased traffic.

Context

MetaMask has roughly 90,000 weekly active users. We anticipate that a small number of these users - at most in the low 1000s, although the number can balloon in the future - may visit an EthDNS website at some point during the week.

Proposal

We want to route our EthDNS traffic through the ipfs.dweb.link gateway. Is this OK?

The text was updated successfully, but these errors were encountered:

rekmarks changed the title MetaMask using *.ipfs.dweb.link for ENS-IPFS sites MetaMask to start using *.ipfs.dweb.link for ENS-IPFS sites? Nov 12, 2019 rekmarks changed the title MetaMask to start using *.ipfs.dweb.link for ENS-IPFS sites? MetaMask to start using *.ipfs.dweb.link for ENS-IPFS sites? Nov 12, 2019 rekmarks mentioned this issue Nov 12, 2019 Ipfs cid v1 base32 MetaMask/metamask-extension#7362 Merged 3 tasks Copy link Member

lidel commented Nov 15, 2019 • edited Loading

Usually we suggest running your own gateway, as .ipfs.dweb.link is provided on best-effort basis, and we may throttle when load becomes too expensive.

@rekmarks FYSA ENS project runs a dedicated gateway at domain .eth.link , which provides not only origin isolation you seek, but also keeps the human-readable ENS name in URL. ENS project should be able to share setup/configs for this too, if you choose to run your own.

Your users will have better experience if you route .eth domains there, and use raw CID gateway such as cid .ipfs.dweb.link only for non- .eth domains.

Including people of interest, you probably want to have a chat with Chris on ENS end:
cc @chris-remus (PM @ensdomains ) @parkan (IPFS collabs) @olizilla (IPFS gateway) @autonome (IPFS in web browsers)

Copy link Author

rekmarks commented Nov 15, 2019

@lidel thank you very much for that answer. We'll plan to use domain .eth.link at least in the short term. We'd love to talk to @chris-remus or whoever is appropriate at @ensdomains .

Copy link

parkan commented Nov 15, 2019

confirming that this is probably the best option in the near term

in the longer term, I would like to gently encourage these users to consider installing companion and/or running a local node

Copy link Member

lidel commented Dec 9, 2019 • edited Loading

@rekmarks @danfinlay

Something I just realized:
MetaMask is using gateway.ipfs.io in production right now: lib/ens-ipfs/setup.js#L48 :P

Having that in mind, I believe it is okay for you to go ahead with MetaMask/metamask-extension#7362 and switch those preexisting code paths to {cid}.ipfs.dweb.link . AFAIK both gateways use the same hosting, so there won't be any difference performance-wise for anyone involved so far, but MetaMask users will get Origin-based isolation mitigating security issues described in MetaMask/metamask-extension#5724 before you figure out alternative hosting or how to use js-ipfs and run this in truly distributed fashion.

I hope this sounds ok to everyone involved.
(cc @olizilla @parkan @autonome for visibility)

Copy link

momack2 commented Dec 10, 2019

@danfinlay and I chatted about swapping over to using the infura gateway so they can send increased load without running into any throttling - not sure if Infura supports subdomain gateway yet?

Copy link Member

lidel commented Dec 10, 2019 • edited Loading

I don't think Infura has it yet. Cloudflare does: https://bafybeiemxf5abjwjbikoz4mc3a3dla6ual3jsgpdr4cjr3oz3evfyavhwq.ipfs.cf-ipfs.com/wiki/

FYSA setting up a subdomain gateway is more difficult than it should , namely go-ipfs should support CID in Host header out of the box. We are tracking improvements on our end in ipfs/kubo#6498

Copy link Author

rekmarks commented Dec 12, 2019 • edited Loading

@lidel we merged MetaMask/metamask-extension#7362 per your previous message. We allow users to specify different CID gateways, but ipfs.dweb.link is the default. Please let us know if anything changes on your end regarding this.

cc: @danfinlay

Edit: I'm fine with closing this issue, but feel free to leave it open for future communications.

Copy link

parkan commented Dec 13, 2019

@egalano can you chime in on

subdomain gateway capability today/using infura gateway here pathway for virtual/delegated node in the future

as per call?

Copy link Contributor

mburns commented May 5, 2020

I think this ticket can be closed, as it has gone quiet. Please re-open if I'm mistaken.

mburns closed this as completed May 5, 2020 Sign up for free to subscribe to this conversation on GitHub . Already have an account? Sign in . Labels None yet 5 participants

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms Privacy Security Status Docs Contact Manage cookies Do not share my personal information You can’t perform that action at this time.
Posted 28 Comments