[Provider] Support fetching avatar metadata stored in ipfs

[christopherdro]

The issue can be reproduced by trying to fetch the avatar for "vitalik.eth"

Error: contentScript.bundle.js:2155 Fetch API cannot load ipfs://ipfs/QmYTuHaoY1winNAxmf7JmCmSrkChuMAAnqgSuJBTiWZe9f. URL scheme "ipfs" is not supported.

The image url is still not entirely correct since the current logic expects the URI to be ipfs://{CID} but the URI returned from the metadata is ipfs://ipfs/{CID}. Any suggestions on the best way to handle this?

[christopherdro]

Related #2271

[ricmoo]

Is that a valid format?

I also don’t mind extending the format to include this as it doesn’t collide with other IPFS and IPNS formats, but I’m curious if there are other common formats too.

[ricmoo]

Also keep in mind that ethers v5 must be ES3-compatible, so it cannot use the URL class.

I’ll make the necessary changes though.

[christopherdro]

Is that a valid format?

Doesn't appear to be. https://docs.ipfs.io/how-to/address-ipfs-on-web/#native-urls

It looks like all the tokens from the Nyan Cat smart contract use this format.

[ricmoo]

This should be fixed as of 5.5.4. Try it out and let me know if there are still any issues.

Thanks! :)