Should we profile CIDs?

Protocol
41

@danieln, after conducting some testing on my end using test-cid-v1-wide, I’m observing a difference in CIDs when a file exceeds 1024 MB.

✅ MATCH for file: file_0_5MB (CID: bafkreie6drn3hggb3ruptdvqlahec5grhjv5m4it3sjvsm7m74us5kbofe)
✅ MATCH for file: file_1023MB (CID: bafybeigggqgfyhwr6okpc2w2v32tu7qczcurpj6j4hii6f4gxjmuot2kci)
✅ MATCH for file: file_1024MB (CID: bafybeih6ciohqseh6blceg35litzlib5we4nqudkeafbp54uu3zh7ld26a)
❌ MISMATCH for file: file_1025MB
   IPFS CID:        bafybeignp2eaklnbejnlcrxaldpiuoc63tk63vdsokleegajxpvczzxiau
   Singularity CID: bafybeia2jsxebrhwuehoptuhpmhmlxhot74nalyihzud2uufosptoakjyu

✅ MATCH for file: file_173MB (CID: bafybeibvtg6kjfyibyej47xr32bg357uh2xffelgricuxziqasdhiyp5ke)
✅ MATCH for file: file_174MB (CID: bafybeig66jfwvfifkpzodebqook26gxcvhlvkqsak35rgvxm2izbob65oy)
✅ MATCH for file: file_175MB (CID: bafybeigwbdeibl3jcugnicgahiqjvdd6f4vyk5sip4ryepk25rll5zi3l4)
✅ MATCH for file: file_1MB (CID: bafkreibksrll5wy37k5z5roemmzciocovqgi4k742a6yz75lpmsgpfukrm)

I tried experimenting with some of the other import options for the ipfs add command, but that didn’t seem to resolve the issue.

I created a Docker image that you can use to recreate it on your end.

The sample data generation configuration profile I used was dataset1, so feel free to remove the others for a quicker turnaround test.

1 Like