-
Notifications
You must be signed in to change notification settings - Fork 986
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
ENS resolving for IPNS names. #10974
Comments
Thanks for adding this @decanus Checking with @churik and @Serhy also noticed that some urls redirect to infura.status.im. Need to invest more time to understand how this works as I'm not sure why e.g. ethereum.eth directs to https://ciqg44hq64xcxtik22n3fmk65hqpj6egsp3lf5ef4sdjtz6w7dn5mkq.infura.status.im Are we using a content hash library by Infura? |
@hesterbruikman all names redirect, thats a correct resolution. |
Signed-off-by: andrey <[email protected]>
Signed-off-by: andrey <[email protected]>
Bug Report
Recently I asked @hesterbruikman why ENS resolving does not work in browser. I was actually wrong on whether or not it works. If you use for example
pactxt.eth
in the browser it resolves. Howeveruniswap.eth
does not.Problem
This is because there was an issue in the contenthash library that did not resolve names correctly when they were IPNS hashes. You can see a more detailed discussion here: ensdomains/ens-app#849. This was recently fixed in ENS which can be viewed here: ensdomains/ui#77.
Expected behavior
Names using IPNS names resolve properly in the browser.
Actual behavior
They currently do not.
Reproduction
uniswap.eth
and hit enterThe text was updated successfully, but these errors were encountered: