Reproducing the CID of an IPFS release artifact
Two publishers can start with identical bytes and calculate different UnixFS roots. A release verifier needs the import recipe as well as the file checksum.
Change one import parameter
Use a multi-megabyte release file for this experiment. Both commands hash the same bytes without storing or advertising them. A larger chunk size changes the boundaries between data blocks and can change the graph that names the file.
ipfs add -Q --only-hash --cid-version=1 --raw-leaves=true --chunker=size-262144 release.bin
ipfs add -Q --only-hash --cid-version=1 --raw-leaves=true --chunker=size-1048576 release.bin
Record enough to reproduce the published root
If the roots differ, compare the producer’s chunker, CID version, leaf encoding and directory wrapping with your settings. A directory root and its child file legitimately have different addresses. If the roots match for a tiny input, repeat with a file large enough to cross a chunk boundary. This test validates the local import recipe; fetching from another peer tests network availability separately.