Bit fun & experiment with hasethereumevergonedown.eth

hello again :pray:
last month I saw apoorv.eth tweeting about hasethereumevergonedown.com
so I reg’d https://hasethereumevergonedown.eth.limo/ and set in a fully inlined ipfs contenthash CIDv1.Raw("<h1>No</h1>") before transferring ownership of that ens domain to apoorv.eth.

@mely.eth :face_with_peeking_eye:

I’m posting this under context as fix(verifcid): enforce size limit for identity CIDs by lidel · Pull Request #1018 · ipfs/boxo · GitHub was merged in sept and there’s clear specs for how much data can we inline with raw/identity, 2x of sha512 hash = max 128 bytes including cidv1 prefix.

cc @ethlimo.eth to support fully raw/inlined contenthash… :vulcan_salute:

screenshot context : CIDv1.eth : onchain raw/cidv1 library - IPFS Forums
&& I hope ENS will update contenthash specs with new ENSIPs to follow these recommendation from IPFS team.

1 Like

We’re looking into this and plan to support it according to the IPFS specs. :saluting_face:

2 Likes

… wish we could get 256 or even 512 bytes max support for gateway-less cidv1/ future v2 in IPFS/ENSIP side?