IPIP 0499: CID Profiles #499
Conversation
src/ipips/ipip-0499.md
Outdated
| 3. Chunk size | ||
| 4. DAG width | ||
| 5. DAG layout | ||
| 6. Required |
There was a problem hiding this comment.
I think there's a word missing here 😅
lets make the fanout match the max links from files and rename profile to `-wide` this will make it easier to discuss in ipfs/specs#499
Co-authored-by: Bumblefudge <bumblefudge@learningproof.xyz>
Import.* config params for controlling DAG width were added in: ipfs/kubo#10774
|
Thank you for kicking this off, and filling initial state. I've incorporated specific "dag width" settings for Next:
|
|
|
||
| #### Empty directories | ||
|
|
||
| Decision if empty directories should be included is left out of scope. |
There was a problem hiding this comment.
@lidel I think we should include this, because the goal of this spec is to make UnixFS encoding deterministic when using the profile, and this stands in the way of this, potentially rendering this whole effort futile if not included.
I think the profile should dictate whether empty directories are included. This should also be configurable such that you can adjust to your own needs.
On the same note, we should probably also add mention of hidden files which are also excluded by Storacha, Kubo, and Helia by default.
| | `HAMTDirectory` threshold | 256KiB (est) | 256KiB (est:links[name+cid]) | 1000 **links** | 256KiB | **1MiB** | not specified | | ||
| | DAG layout | balanced | balanced | balanced | balanced | balanced | not specified | | ||
| | Leaves | raw | raw | raw | raw | raw | not specified | | ||
| | Empty directories | allowed | allowed | disallowed | allowed | allowed | not specified | |
There was a problem hiding this comment.
It's about the default behaviour rather than whether empty dirs are allowed.
|
|
||
| ### User benefit | ||
|
|
||
| Reliable, deterministic CIDs allow independent verification of content across tools and ipmlementations. |
There was a problem hiding this comment.
| Reliable, deterministic CIDs allow independent verification of content across tools and ipmlementations. | |
| Reliable, deterministic CIDs allow independent verification of content across tools and implementations 8000 . |
|
@jaller94 / @mishmosh, I've noticed a discrepancy in CID generation using the new This could be an edge case, as I'd expect the same CID to be generated. If necessary, would either of you be able to point me to a repo within the |
Currently, CIDs can be generated with a variety of settings and optimizations for chunking, DAG width, and more. This means the same file can yield multiple, different CIDs depending on which tools and settings are used, and it is not possible to reliably reproduce or verify the CID.
This proposal introduces profiles for IPFS CIDs. Profiles explicitly define CID version, hash algorithm, chunk size, DAG width, layout, and other parameters. They can be used to verify data across implementations, provide recommended settings depending on retrieval performance goals, and more.