Use CIDv1 with 1MiB chucks --> kubo test-cid-v1-wide profile

[agmap]

I have noticed that the CIDs do not match the CIDs generated by Storacha, ipfs/helia, and IPFSDesktop.
Please update your kubo to v0.37.0 and apply test-cid-v1-wide profile.
See: https://github.com/ipfs/kubo/blob/master/docs/config.md#test-cid-v1-wide-profile
This will undoubtedly become the standard for CIDv1, so we must integrate it as soon as possible.

[rrbin666]

Hi, thanks a lot for raising this issue and for sharing your observations.

As far as I know, the test-cid-v1-wide profile is still considered an experimental setting in Kubo. Do you happen to know if there is a clear timeline for when it will be stabilized or made the default?

Also, could you share more details about your use case? I’d like to better understand how not upgrading affects your workflow or interoperability with Storacha, Helia, or IPFS Desktop. This will help us evaluate the priority and potential impact of adopting this profile sooner.

[agmap]

@rrbin666 Thank you very much for looking into that issue. 🙏

As far as I know, 1 MiB chucks are increasingly becoming the standard in the IPFS ecosystem. (Stroracha, Lighthouse, ipfs/helia, kubo ...)
Regarding the timeline for implementation in kubo: by the end of 2025?? For more details, please contact IPFS Shipyard directly. I have been using the advanced, more modern test-cid-v1-wide profile in my own kubo/ipfs desktop for quite some time now without any problems.

I want my CID to be widely distributed across the ipfs network and not just with one provider like currently:
Example:
https://check.ipfs.network/?cid=bafybeickcbyh7zgkhx7eaqceujayrk7nzwf7d7ftz256r5e2zpcrzzlhiy&multiaddr=&ipniIndexer=https%3A%2F%2Fcid.contact&timeoutSeconds=30&httpRetrieval=on

That's why I usually upload the data to Storacha again, or use libraries like ipfs/helia.
The data is only distributed across multiple providers in the ipfs network if identical CIDs are generated.
If that is not the case, then I can only transfer the data to the alternative IPFS providers via CAR file download/upload.
Hence my other issue. #18

I also strongly recommend upgrading to the new kubo v0.38.0. Here, data is announced in Amino DHT much faster and in a more resource-efficient manner. 💯🚀👍

[agmap]

According IPIP-499 the new profile is now called: unixfs-v1-2025