If anything goes wrong while we're unpacking the CID, because of a malformed CID or we have a bug, then the error is currently just logged to the console.

Malformed CID errors should be show to the user, a form that helps them figure out what's wrong with their CID where possible.

Add telemetry according to ipfs/ipfs-gui#105.

See ipfs/ipfs-gui#105 (comment) for more
details about why there is no UI treatment.

Users will be able to opt out by executing the function removeMetricsConsent in their browser console: removeMetricsConsent(). They can re-add consent using addMetricsConsent().

Problem:

• https://cid.ipfs.io/#k2cwueckqkibutvhkr4p2ln2pjcaxaakpd9db0e7j7ax1lxhhxy3ekpv
• https://cid.ipfs.io/#k51qzi5uqu5dj16qyiq0tajolkojyl9qdkr254920wxv7ghtuwcz593tp69z9m (inlined ED25519)

Context:

• ipfs/go-cid#107
• ipfs/kubo#7318

Please review multiformats/cid#26

for reference:

https://cid.ipfs.io/#baguqeeranycvebnhdwjwaimaylo2lon5h22ueqdto74e5wnfnm7rspq4or7q

shows code is 0xa902 where the actual JSON code is 0x0129. The former is the varint encoding of the latter, but misleading because it's the wrong code and isn't decoded

the ipfs block commands work with multihashes rather than CIDs. It would he helpful to be able to paste in a CID and see it's base encoded multihash that could be pasted into one of those commands.

in the meantime you can

$ ipfs --offline cid format -f %m zb2rhe5P4gXftAwvA4eXQ5HJwsER2owDyS9sKaQRRVQPn93bA                                                                                                 
zQmVmkadKS2uvxyD6YJJzd3Umem6SWV7QxYnL7kbpdWAsPS

There is a multicodec for CARs now. CIDs exist in the wild for them. This site can't decode them yet as it's got an old version of the multicodecs table.

The old ways must give way to the new. multicodecs is not updated. multiformats is where the action is.

As suggested by @ribasushi It might be worth reworking this site so that we don't have to redeploy it every time the table is updated. Historical note, it was built this way so that it was self contained, and the site would work entire offline if you have the dag for the site root.

Link to this repo from the tool itself so that people can open issues if things don't work as expected or if they have ideas for improvements.

Add a CID builder that lets you create a CID from drop downs for each multiformat, or let's you paste in a human CID to get the encoded version out.

As noted in #45 we switched to GithubActions and want to disable CircleCI builds at:
https://app.circleci.com/jobs/github/multiformats/cid-utils-website/68

I don't have access to Mutliformats org.
Perhaps @rvagg @warpfork can help?

...or spec should match what this site does.

https://github.com/multiformats/cid#human-readable-cids

# corresponding human readable CID
base58btc - cidv1 - raw - sha2-256-256-6e6ff7950a36187a801613426e858dce686cd7d7e3c0fc42ee0330072d245c95

https://cid.ipfs.io/#zb2rhe5P4gXftAwvA4eXQ5HJwsER2owDyS9sKaQRRVQPn93bA

Human readable CID
base58btc - cidv1 - raw - (sha2-256 : 256 : 6E6FF7950A36187A801613426E858DCE686CD7D7E3C0FC42EE0330072D245C95)

I often need v0 for cloudflare compatibility.

There is already v0 to v1 convertor

Would be super useful as cid utils website is my primary way of decoding Filecoin code CIDs.
Example https://cid.ipfs.io/#bafkqadtgnfwc6mjpnv2wy5djonuwo

If you modify https://cid.ipfs.io/#bafk2bzaceaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa to be one character shorter than it should be, all the information disappears save for the multihash length inconsistent: error even though the valid multibase, multicodec, etc, are still present. It'd be nice if only certain sections were omitted when invalid parameters were present.

Similar problem as #43. IPFS now supports emoji CIDs adn cid.ipfs.io does not.

example from @ribasushi
https://cid.ipfs.io/#🚀🪐⭐💻😅❓💎🌈🌸🌚💰💍🌒😵🐶💁🤐🌎👼🙃🙅☺🌚😞🤤⭐🚀😃✈🌕😚🍻💜🐷⚽✌😊

The main blocker here is that to fix it the guts of the site will have to be rewritten to use the new multiformats lib

If the CID use the libp2p-key codec (example), it would be pretty neat to also decode the embedded public key, according to https://github.com/libp2p/specs/blob/master/peer-ids/peer-ids.md.

this should be an error https://cid.ipfs.tech/#zQmTFGZgypZBYozPTF2qqeho5n17MJXSkHRMDhRqmkroAZu

see: multiformats/js-multiformats#240

currently it shows the multibase as "implicit" but it's been explicitly set... and a CID v0 should not have a multibase prefix.

This is already implemented in js, just the deps need to be bumped
multiformats/js-multihash#75 (comment)

The http://cid-utils.ipfs.team/ website returns 404 Not Found.

https://cid.ipfs.io/#bafk2bzaceaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa tells the user about the CID, however, it'd be nice if some of the parameters were dropdowns so you could see what the CID looks like if slightly changed.

e.g. Changing Name: base32 to Name: base36 with a dropdown menu that shows all multibases available. This is especially useful since some encodings mean the characters don't neatly align to a single, whole byte each.

It might also be of benefit to give the user the option to manually type in multiformat codes to see how non-standard multiformats would be encoded.

We should have a test for each:

• CIDv0 (QmbWqxBEKC3P8tqsKc98xmWNzrzDtRLMiMPL8wBuTGsMnR)
• CIDv1 base32
  • dag-pb
  • raw
  • dag-json
  • dag-cbor
• CIDv1 base36
  • libp2p-key codec
• PeerID (not a CID, but pasting 12D3KooWJHxkQKX8C5KAyqEPhn2ssT2in4TExyG9SXxi519tycL9 should show meaningful error as noted in #48)

Context: https://github.com/libp2p/specs/blob/master/RFC/0001-text-peerid-cid.md

In short, PeerIDs are not CIDs, but can be represented as one (CIDv1 with libp2p-key codec).

Due to this, easy UX win is to detect raw PeerID like 12D3KooWJHxkQKX8C5KAyqEPhn2ssT2in4TExyG9SXxi519tycL9
and should show meaningful error that pasted identifier is not a CID, but can be represented as one, and show the CIDified version:

$ ipfs id --peerid-base base36 12D3KooWJHxkQKX8C5KAyqEPhn2ssT2in4TExyG9SXxi519tycL9 --offline | jq  .ID
k51qzi5uqu5djbl2zsl8ooauuh7wb1ycesq93g72iym71shji1pbntl1vuyuk2

After the new Anatomy of a CID ProtoSchool tutorial is launched (based on Alan's IPFS Camp session), I'll circle back and add a CTA here to go learn more about CIDs there.

Blocked by ProtoSchool/protoschool.github.io#359

FYI @zebateira

Just noticed that the CID Inspector, unlike the Block Explorer, is missing a favicon. Would be great to copy that one over.

Implement metrics in this project

• #56
• #57

Additional context

• ipfs/ipfs-gui#105
• ipfs/ipfs-gui#117
• https://github.com/ipfs-shipyard/ignite-metrics/blob/main/docs/telemetry/COLLECTION_POLICY.md

It would be useful to know how long a CID is in bytes.

This would be especially useful for folks storing CIDs in space constraints environments like blockchains.

This was also partially inspired by Ryan's blog post https://blag.thedisco.zone/?post=cidfacts

Let's say I have a v0 CID:

QmXS8zmXsBVGvdPzj3QFVrzJUcKaaUkEVhHMFvgxUJdVFT
I can convert it to a v1 CID:

$ ipfs cid base32 QmXS8zmXsBVGvdPzj3QFVrzJUcKaaUkEVhHMFvgxUJdVFT
bafybeieheejcn4tspx5re74waw2ixp6hw6rvsssjlf6c3eivcy7oooqjay
But that got longer, so what if I wanted to include it in an NFT, using as little data as possible? Well then I'd use the [identity base with raw encoding](https://github.com/multiformats/multicodec/blob/master/table.csv):

$ ipfs cid format -b identity -c raw bafybeieheejcn4tspx5re74waw2ixp6hw6rvsssjlf6c3eivcy7oooqjay
p ?!&?r}?????Ƿ?YJIY|-?>?:
We went from our 46 byte v0 CID, to a 59 byte v1 CID, to a 37 byte raw CID. We can easily go back the same way we initially got the v1 CID as well:

$ ipfs cid format -b identity -c raw bafybeieheejcn4tspx5re74waw2ixp6hw6rvsssjlf6c3eivcy7oooqjay > rawcid
$ cat rawcid | ipfs cid base32
bafybeieheejcn4tspx5re74waw2ixp6hw6rvsssjlf6c3eivcy7oooqjay