Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.
https://github.com/multiformats/cid

Self-describing content-addressed identifiers for distributed systems
https://github.com/multiformats/cid
cid ipfs ipld multiformats
Last synced: 2 months ago
JSON representation
Self-describing content-addressed identifiers for distributed systems
Host: GitHub
URL: https://github.com/multiformats/cid
Owner: multiformats
License: other
Created: 2016-09-09T16:04:53.000Z (almost 8 years ago)
Default Branch: master
Last Pushed: 2023-12-15T03:31:54.000Z (7 months ago)
Last Synced: 2024-02-04T17:31:57.302Z (5 months ago)
Topics: cid, ipfs, ipld, multiformats
Homepage:
Size: 51.8 KB
Stars: 401
Watchers: 39
Forks: 94
Open Issues: 12
Metadata Files:
- Readme: README.md
- License: LICENSE
Lists

awesome-list - cid - describing content-addressed identifiers for distributed systems | multiformats | 250 | (Others)
awesome-starred - multiformats/cid - Self-describing content-addressed identifiers for distributed systems (ipfs)
awesome-data-integrity - Content IDentifer
README

        # CID (Content IDentifier) Specification

[![](https://img.shields.io/badge/made%20by-Protocol%20Labs-blue.svg?style=flat-square)](https://protocol.ai/)

[![](https://img.shields.io/badge/project-ipld-blue.svg?style=flat-square)](https://github.com/ipld/ipld)

[![](https://img.shields.io/badge/freenode-%23ipfs-blue.svg?style=flat-square)](https://webchat.freenode.net/?channels=%23ipfs)

> Self-describing content-addressed identifiers for distributed systems

## Table of Contents

  - [Motivation](#motivation)

  - [What is it?](#what-is-it)

  - [How does it work?](#how-does-it-work)

  - [Design Considerations](#design-considerations)

  - [Variant Representation - Internal CID](#variant-representation---internal-cid)

  - [Variant Representation - Human Readable CID](#variant-representation---human-readable-cid)

  - [Versions](#versions)

    - [CIDv0](#cidv0)

    - [CIDv1](#cidv1)

  - [Decoding Algorithm](#decoding-algorithm)

  - [Implementations](#implementations)

  - [FAQ](#faq)

  - [Maintainers](#maintainers)

  - [Contribute](#contribute)

  - [License](#license)

## Motivation

[**CID**](https://github.com/ipld/cid) is a format for referencing content in distributed information systems, like [IPFS](https://ipfs.io). 

It leverages [content addressing](https://en.wikipedia.org/wiki/Content-addressable_storage), [cryptographic hashing](https://simple.wikipedia.org/wiki/Cryptographic_hash_function), and [self-describing formats](https://github.com/multiformats/multiformats). 

It is the core identifier used by [IPFS](https://ipfs.io) and [IPLD](https://ipld.io). 

It uses a [multicodec](https://github.com/multiformats/multicodec) to indicate its version, making it fully self describing.

**You can read an in-depth discussion on why this format was needed in IPFS here: https://github.com/ipfs/specs/issues/130 (first post reproduced [here](./original-rfc.md))**

## What is it?

A CID is a self-describing content-addressed identifier. 

It uses cryptographic hashes to achieve content addressing. It uses several [multiformats](https://github.com/multiformats/multiformats) to achieve flexible self-description, namely:

1. [multihash](https://github.com/multiformats/multihash) to hash content addressed, and

2. [multicodec](https://github.com/multiformats/multicodec) to type that addressed content,

to form a binary self-contained identifier, and optionally also

3. [multibase](https://github.com/multiformats/multibase) to encode that binary CID as a  string.

Concretely, it's a *typed* content address: a tuple of `(content-type, content-address)`.

## How does it work?

Current version: CIDv1

CIDv1 is a **binary** format composed of [unsigned varints](https://github.com/multiformats/unsigned-varint) prefixing a hash digest to form a self-describing "content address":

```text

 ::= 

# or, expanded:

 ::= <`0x01`, the code for `CIDv1`>

```

Where

- `` is a [multicodec](https://github.com/multiformats/multicodec) representing the version of CID, here for upgradability purposes.

- `` is a [multicodec](https://github.com/multiformats/multicodec) code representing the content type or format of the data being addressed.

- `` is a [multihash](https://github.com/multiformats/multihash) value, which uses a registry of hash function abbreviations to prefix a cryptographic hash of the content being addressed, thus making it self-describing.

## Variant - Stringified Form

Since CIDs have many applications outside of binary-only contexts, a given CID may need to be base-encoded multiple ways for different consumers or for different transports. 

In such applications, CIDs are often expressed as a Unicode *string* rather than a bytestring, which adds a single code-point prefix. 

In these contexts, then, the full string form is:

```text

 ::= )>

```

Where

- `` is a [multibase](https://github.com/multiformats/multibase) prefix  (1 Unicode code point in length) that renders the base-encoded unicode string following it self-describing for simpler conversion back to binary.

## Variant - Human-Readable Form

It is often advantageous to translate a CID, which is already modular and self-describing, into a *human-readable* expansion of its self-describing parts, for purposes such as debugging, unit testing, and documentation. 

We can easily transform a Stringified CID to a "Human-Readable CID" by translating and segmenting its constituent parts as follows:

```text

 ::=  "-"  "-"  "-" 

```

Where each sub-component is replaced with its own human-readable form from the relevant registry:

- `` is the name of the multibase code (eg `z`--> `base58btc`)

- `` is the name of the multicodec for the version of CID used (eg `0x01` --> `cidv1`)

- `` is the name of the multicodec code (eg `0x51` --> `cbor`)

- `` is the name of the multihash code (eg `sha2-256-256`) followed by a final dash and the hash itself `-abcdef0123456789...`)

For example:

```text

# example CID

zb2rhe5P4gXftAwvA4eXQ5HJwsER2owDyS9sKaQRRVQPn93bA

# corresponding human readable CID

base58btc - cidv1 - raw - sha2-256-256-6e6ff7950a36187a801613426e858dce686cd7d7e3c0fc42ee0330072d245c95

```

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

## Design Considerations

CIDs design takes into account many difficult tradeoffs encountered while building [IPFS](https://ipfs.tech). These are mostly coming from the multiformats project.

- Compactness: CIDs are binary in nature to ensure these are as compact as possible, as they're meant to be part of longer path identifiers or URIs.

- Transport friendliness (or "copy-pastability"): CIDs are encoded with multibase to allow choosing the best base for transporting. For example, CIDs can be encoded into base58btc to yield shorter and easily-copy-pastable hashes.

- Versatility: CIDs are meant to be able to represent values of any format with any cryptographic hash.

- Avoid Lock-in: CIDs prevent lock-in to old, potentially-outdated decisions.

- Upgradability: CIDs encode a version to ensure the CID format itself can evolve.

## Versions

### CIDv0

CIDv0 is a backwards-compatible version, where:

- the `multibase` of the string representation is always `base58btc` and implicit (not written)

- the `multicodec` is always `dag-pb` and implicit (not written)

- the `cid-version` is always `cidv0` and implicit (not written)

- the `multihash` is written as is but is always a full (length 32) sha256 hash.

```text

cidv0 ::= 

```

### CIDv1

See the section: [How does it work?](#how-does-it-work)

```text

 ::= 

```

## Decoding Algorithm

To decode a CID, follow the following algorithm:

1. If it's a string (ASCII/UTF-8):

  * If it is 46 characters long and starts with `Qm...`, it's a CIDv0. Decode it as base58btc and continue to step 2.

  * Otherwise, decode it according to the multibase spec and:

    * If the first decoded byte is 0x12, return an error. CIDv0 CIDs may not be multibase encoded and there will be no CIDv18 (0x12 = 18) to prevent ambiguity with decoded CIDv0s.

    * Otherwise, you now have a binary CID. Continue to step 2.

2. Given a (binary) CID (`cid`):

   * If it's 34 bytes long with the leading bytes `[0x12, 0x20, ...]`, it's a CIDv0.

     * The CID's multihash is `cid`.

     * The CID's multicodec is DagProtobuf

     * The CID's version is 0.

   * Otherwise, let `N` be the first varint in `cid`. This is the CID's version.

     * If `N == 0x01` (CIDv1):

       * The CID's multicodec is the second varint in `cid`

       * The CID's multihash is the rest of the `cid` (after the second varint).

       * The CID's version is 1.

     * If `N == 0x02` (CIDv2), or `N == 0x03` (CIDv3), the CID version is reserved.

     * If `N` is equal to some other multicodec, the CID is malformed.

## Implementations

- [go-cid](https://github.com/ipfs/go-cid)

- [java-cid](https://github.com/ipld/java-cid)

- [js-multiformats](https://github.com/multiformats/js-multiformats)

- [rust-cid](https://github.com/multiformats/rust-cid)

- [py-multiformats-cid](https://github.com/pinnaculum/py-multiformats-cid)

- [elixir-cid](https://github.com/nocursor/ex-cid)

- [dart_cid](https://github.com/dwyl/dart_cid)

- [Add yours today!](https://github.com/multiformats/cid/edit/master/README.md)

## FAQ

> **Q. I have questions on multicodec, multibase, or multihash.**

Please check their repositories: [multicodec](https://github.com/multiformats/multicodec), [multibase](https://github.com/multiformats/multibase), [multihash](https://github.com/multiformats/multihash).

> **Q. Why does CID exist?**

We were using base58btc encoded multihashes in IPFS, and then we needed to switch formats to IPLD. 

We struggled with lots of problems of addressing data with different formats until we created CIDs. 

You can read the history of this format here: https://github.com/ipfs/specs/issues/130

> **Q. Is the use of multicodec similar to file extensions?**

Yes, kind of! like a file extension, the multicodec identifier establishes the format of the data. 

Unlike file extensions, these are in the middle of the identifier and not meant to be changed by users.

There is also a short table of supported formats.

> **Q. What formats (multicodec codes) does CID support?**

We are figuring this out at this time. 

It will likely be a subset of [multicodecs](https://github.com/multiformats/multicodec/blob/master/table.csv) for secure distributed systems. 

So far, we want to address IPFS's UnixFS and raw blocks ([`dag-pb`](https://ipld.io/specs/codecs/dag-pb/spec/), [`raw`](https://www.iana.org/assignments/media-types/application/vnd.ipld.raw)), IPNS's [`libp2p-key`](https://github.com/libp2p/specs/blob/master/RFC/0001-text-peerid-cid.md), and IPLD's [`dag-json`](https://ipld.io/specs/codecs/dag-json/spec/)/[`dag-cbor`](https://ipld.io/specs/codecs/dag-cbor/spec/) formats.

> **Q. What is the process for updating CID specification (e.g., adding a new version)?**

CIDs are a well established standard. 

IPFS uses CIDs for content-addressing and IPNS.

Making changes to such key protocol requires a careful review which should include feedback from implementers and stakeholders across ecosystem.

Due to this, changes to CID specification MUST be submitted as an improvement proposal to [ipfs/specs](https://github.com/ipfs/specs/tree/main/IPIP) repository (PR with [IPIP document](https://github.com/ipfs/specs/blob/main/IPIP/0000-template.md)), and follow the IPIP process described there. 

## Maintainers

Captain: [@jbenet](https://github.com/jbenet).

## Contribute

Contributions welcome. Please check out [the issues](https://github.com/ipld/cid/issues).

Check out our [contributing document](https://github.com/ipld/ipld/blob/master/contributing.md) for more information on how we work, and about contributing in general.

Please be aware that all interactions related to IPLD are subject to the IPFS [Code of Conduct](https://github.com/ipfs/community/blob/master/code-of-conduct.md).

Small note: If editing the README, please conform to the [standard-readme](https://github.com/RichardLitt/standard-readme) specification.

## License

This repository is only for documents.

These are licensed under a [CC-BY 3.0 Unported](LICENSE) License © 2016 Protocol Labs Inc.