Add support for ZeroNet

[filips123]

Add support for ZeroNet site address in ENS domains. This depends on pldespaigne/content-hash#33 and it is related to ensdomains/ui#23. Changes in content-hash are now released in 2.4.4.

[Gudahtt]

The PR this depends on was now closed: pldespaigne/content-hash#33

I'm guessing this PR won't work until content-hash is updated to v2.4.4.

[filips123]

@Gudahtt Changes from that Pr were implemented in a slightly different way. Yes, content-hash needs to be updated to v2.4.4. I will update it soon.

[filips123]

@Gudahtt I updated content-hash to 2.4.4. However, for some reason, I can't update lock file with Yarn, so I only updated package.json (this is why CI failed). You can now merge this PR and update lock file.

[Gudahtt]

@filips123 I've just rebased this and updated the lock file.

How would we go about testing this? Would you mind testing this latest version? I'm not familiar with ZeroNet

[filips123]

@Gudahtt What testing should this be?

ZeroNet works so that the website is accessed at http://127.0.0.1:43110/ADDRESS/PATH (similar to IPFS and Swarm gateways). Here, address is stored in ENS domain as content-hash and path is from the original URL. So, it should work correctly.

Testing on actual domains would be a bit harder because there are currently no ZeroNet ENS domains, and ENS manager PR is currently still not merged.

[Gudahtt]

We're going to merge this for now, but going forward we may ask that anybody adding additional protocols to the ENS resolver wait for the plugin system, and implement it as a plugin.

We do want to support EIP-1577, but we're not eager to take on the maintenance burden of supporting every possible protocol that an ENS name could map to. Plugins would allow us to safely accept additional protocols maintained by third parties, and it would also allow users to disable protocols if they'd prefer. We will likely migrate these existing protocols to plugins as well.

[filips123]

@Gudahtt Thank you! Do you also have any evidence when my ENS Manager PR (ensdomains/ui#23) will be merged? Because without it, there isn't any easy way to create such domains (although you can programatically manually register it with Web3 librrary).

[Gudahtt]

Unfortunately not! I'm not involved with that library. Best of luck getting that merged though.

[filips123]

Ok, thanks anyway.