-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Unstoppable Domains IPFS for local gateway should show ipfs:// #15750
Comments
How does Ethereum resolution work? If it is using https://resolver.unstoppable.io/dns-query or https://eth.resolver.cloudflare-eth.com/dns-query then we will be able to keep |
@lidel Currently it calls Unstoppable Domains smart contract via eth_call when visiting *.crypto, if there's IPFS content hash record existed, we'll redirect to ipfs://{CID} using that. |
@yrliou is Brave running own Ethereum light client, or is the |
@lidel currently we do eth_call via Infura. |
Ack. In that case we need to wait for go-ipfs 0.9.0, and we will be able to show |
UD set as Ethereum, ipfs as local node:
|
We should start work towards supporting |
Note that the behavior with 0.7.0 is pointing the user at a static snapshot – the user may not understand this is an immutable version, and if they bookmark |
Verified
Steps:
|
When Unstoppable Domains is set to resolve via Ethereum, and the local gateway is in use, we resolve to an IPFS URI like:
http://bafybeihihoci7ocqupvuda3ldpiy5zvjctgybg32jxpppplkstdwtq7dhi.ipfs.localhost:48081/
Instead we should show ipfs:// in that case.
The text was updated successfully, but these errors were encountered: