You can paste any IPFS CID into the handy CID Inspector to visualize all of its prefixes and what they represent.
In this final lesson we will take a look at some results from this tool using both CIDv0 and CIDv1 formats.
This first example is a version 1 CID.
Looking at the results from the CID Inspector tool we can see several parts that the tool was able to parse for us:
Human Readable CID: breaks down each part of the CID to be easily readable by us humans
codeis the identifier of the base, in this case
codeis the identifier of the codec, in this case
dag-pb, an IPLD format
Multihash: breakdown of the multihash into the hashing algorithm used (
18is the code for
sha2-256), the length of the hash (256 bits, which equates to 32 bytes), and the content hash itself (digest hex).
From the "Human Readable CID" breakdown, we can see that the original hash of the content, before the appropriate CIDv1 prefixes are added, is
This Version 0 CID shows some different results: both the
multibase and the
multicodec are listed as "implicit".
Since Version 0 CIDs did not have those prefixes, they are always assumed to be
Base32 CIDV1 label we see
bafybeigdyrzt5sfp7udm7hu76uh7y26nf3efuylqabf3oclgtqy55fbzdi, which is the same CID from the first example! The CID Inspector has offered us a conversion from CIDv0 to CIDv1.
Notice also how the end of the "Human Readable CID" (the portion after the prefixes) is exactly the same in this CIDv0 example as it was in the CIDv1 example:
Why? These two CIDs point to the same content. Basically, it's the same hash (
C3C4733EC8AFFD06CF9E9FF50FFC6BCD2EC85A6170004BB709669C31DE94391A) represented in the two different versions of the CID spec.
You can convert any
CIDv1, because the implicit prefixes from
v0 become explicit in
CIDv1 supports multiple codecs and multiple bases and
CIDv0 does not, not all
CIDv1 can be converted to
CIDv0. In fact, only
CIDv1 that have the following properties can be converted to
multibase = base58btc
multicodec = dag-pb
multihash-algorithm = sha2-256
multihash-length = 32(32 bytes, equivalent to 256 bits)
To test this theory, you can check out our beloved aardvark image here, hosted on the IPFS network: https://ipfs.io/ipfs/QmcRD4wkPPi6dig81r5sLj9Zm1gDCL4zgpEj9CfuRrGbzF
v0CID with the converted
v1CID in the original URL and refresh the page
You should see the same image of our aardvark.