Hello again :folded_hands: from namesys.eth This is our standalone libraries for onchain raw/cidv1 encoders. Multicodecs: dag-cbor, dag-json, dag-pb, json-utf8, raw-bin, unix-fs Multihashes: identity-raw, keccak-256, sha-256 [image] GitHub - namesys-eth/cidv1.eth: onchain cidv1 …

Thanks for the context. I understand why you chose this approach. However, relying on echoing back and forth unlimited data inlining is risky from the long term perspective. Current situation: Your code works today because there’s no size limit on inlined data yet and gateways echo it back. But thi…

Hi, bunch of things to unpack here, but need to learn more about your use case. Do you mind sharing example of “long CIDs” that do not work for you? [image] 0xc0de4c0ffee: Multihashes: identity-raw, keccak-256, sha-256 CIDs for *-256 ones are 32 bytes in length, so how are you producing CI…

[image] lidel: Is there a specification for “concat” approach eth.limo did? RFC 4408 used to format longer SPF and TXT records. [image] lidel: Inlining a lot of data (>32 bytes) using identity one? That sounds like an antipattern but lmk if I misread the situation (CID examples would hel…

[image] 0xc0de4c0ffee: RFC 4408 used to format longer SPF and TXT records. RFC 4408 deals with concatenating multiple TXT records for longer SPF entries, but DNS label limits (63 characters per label, 253 total for FQDN) seem to be a separate constraint of the DNS system. Could you clarify …

:folded_hands: err, sorry for bit late reply, I thought I already posted this, but it was still in draft.. so addin bit more context/origin story. [image] lidel: What is a.. “dynamic” CID? I’m honestly puzzled by the mention of “dynamic cidv1” - CIDs by definition represent immutable content. …

Hi @0xc0de4c0ffee , FYSA the currently adopted (Boxo GO/Helia JS) limit is 128 bytes: IPIP-0512: Limit Identity CID Size to 128 Bytes in UnixFS Contexts If you believe there is a sensible use case for increasing it for the entire IPFS ecosystem, feel free to o…

[image] lidel: This characterization seems misleading. The example actually relies entirely on a gateway to deserialize data and return the content to the client—it’s not truly “no-gateway” delivery. While current ENS services like eth.limo use ipfs node/gateways to retrieve those inlined dat…

Interesting, I think it’s worth distinguishing between use cases here. Inlining small JSON data (like the <ens/0xaddr>.nftclub.eth example returning account balances) seems reasonable - the data itself is onchain and verifiable, just encoded efficiently in a CID when small. Fair enough, as long you…

[image] lidel: <meta http-equiv="refresh" content="0;url=https://domain.com/user"/> What’s the use case for this? Vanity URLs? Bridging to regular websites? I added that as an example for simple raw html/text.. I’d use _redirect specs if real redirect is required.. simple use case is for tin…

Thank you for explanation. Feel free to open new IPIP arguing why the limit should be increased, but the use cases does not look compelling beyond 128 bytes: when I wrote IPIP-512 nobody in IPFS ecosystem thought inlining bigger amounts of data is a good idea, everyone seemed to be happy to lock t…

CIDv1.eth : onchain raw/cidv1 library

0xc0de4c0ffee November 22, 2025, 6:03pm 7

hello again..
it’d be really^3 nice to have 256 bytes or even 512 bytes at max inline support for future..

Topic		Replies	Views
[deprecate] IPFS ❤️ human readable URLs - Use a DHT to upgrade URLs to IPFS-CIDs Protocol content-discovery	8	1305	March 9, 2021
CID concept is broken Ecosystem and Usage	68	4948	February 2, 2022
Should we profile CIDs? Protocol	51	1698	March 16, 2026
How to convert from hex to CID Help js-ipfs	15	3562	July 1, 2021
Uploading CARs and user generated CIDs web3storage , rant	14	719	April 14, 2026

CIDv1.eth : onchain raw/cidv1 library

Related topics