content field does not allow to pass cidv1 hash for ipfs hashes

[wighawag]

The current website does not allow me to enter ipfs hash in cidv1 format like ipfs://bafybeidkapzich7dcpsouvpuv4vm6gf5mniohqwir2xvo4mldvxkrgtwva

[jefflau]

@pldespaigne Is this something that needs to be updated in the contenthash library?

[pldespaigne]

everything is here ^^
#538

[jefflau]

@pldespaigne Apologies, the migration stuff was crazy - will get @makoto to catch up on it ASAP!

[makoto]

hey, @pldespaigne sorry for taking ages for taking a look. Would you mind describing what and how I should test? I just did the following 2 tests and both are failing.

1. Trying to set ipfs://bafybeidkapzich7dcpsouvpuv4vm6gf5mniohqwir2xvo4mldvxkrgtwva in content section shows an error message (just like @wighawag is encountering). Would ui change PR actually allow to encode cidv1?

2. Trying to set the cidv0 (ipfs://QmaEBknbGT4bTQiQoe2VNgBJbRfygQGktnaW5TbuKixjYL) will allow me to send a transaction to set the content in ENS, but now decoding as empty when displaying as it is throwing at contents.js:91 Error encoding content hash. If you remove try/catch, it is actually failing to decode at encoded = '0x' + contentHash.fromIpfs(content).

[brantlymillegan]

Hey @pldespaigne, just checking on this. Any ideas re Makoto's questions above?

[makoto]

Closing due to inactivity