✔️ Issue #5742 update ens resolver to eip 1577

[pldespaigne]

For solving this issue I have used a small lib called content-hash. I have developped this lib to implement the content-hash encoding specified by the EIP1577. The code of the lib can be found here. This lib is trusted by the ENS team and it is currently used in the official ENS manager web app (discussion here, commit here).
Because the purpose of the content-hash lib is to solve this exact issue, I have included it in the package.json file.

Detailed realisations :

• resolve eip1577 compliant swarm content-hash to the swarm gateway
• resolve eip1577 compliant ipfs content-hash to the ipfs gateway
• resolve legacy swarm content to the swarm gateway
• redirect to the ENS manager on error
• use ENS logo on the loading page

You can test on ropsten with those link
errordomain.eth -> error : redirect to the ENS manager
dappsnation.eth -> legacy swarm content
ipfs.dappsnation.eth ->ipfs content-hash
swarm.dappsnation.eth ->ipfs content-hash

[pldespaigne]

see issue #5742

[pldespaigne]

@danfinlay @kumavis this is ready for review 😁

[pldespaigne]

Guys ? Is there anybody to review my PR ?
@danfinlay @kumavis @bdresser

[tmashuang]

Will need to fix package-lock conflicts, since it's been updated after this PR. Regression, so we aren't allowing access to legacy domains like http://portalnetwork.eth?

[pldespaigne]

• This PR supports legacy resolver with content field as defined by the old ens docs
• It support the new contenthash field as defined by the EIP1577
• It does NOT supports multihash field as proposed by EIP1062
• It does NOT supports ipfs content resolution via text['dnslink'] ala Dappnode

multihash is not widely used and kinda deprecated by contenthash and resolution via the text field is not standard at all and used solely by Dappnode. Moreover it is really hard to find doc about both, that's why I haven't implemented them into this PR. I could do it if needed but I'm not sure it is a good idea, @Arachnid what are your thought about that ?

PS: Here you can read discussion about the EIP1062, dappnode and the EIP1577.

[Arachnid]

@pldespaigne I think supporting only content (as legacy) and contenthash is the best way to go.

[tmashuang]

Looks good to me then, just need to resolve the package-lock.json. A quick solution would be to rebase with develop, remove the package-lock.json, npm i, and commit the new package-lock.json.

[pldespaigne]

@danfinlay @bdresser @kumavis @whymarrh The conflict is solved, I just need a review now :)