IPLD
The What and Why of IPLD
This Launchpad site is now deprecated. To see the newest information and learn more about IPFS, Filecoin, and everything else we will add, continue to our new curriculum page at https://curriculum.pl-launchpad.io/.
IPLD (InterPlanetary Linked Data) is The Data Layer for content-addressed systems. It deals with all the heavy lifting in IPFS; it represents data as Merkle-DAGs with roots identified by content IDs called CIDs.
Why IPLD?
IPLD answers the question: Can we extract a re-usable data layer from IPFS that can be used to build other types of content-addressed data systems?
Every content addressed system reinvents the data layer, typically in non-reusable ways. But we think that building the next Git should take hours, not days! so IPLD aims to be an off-the-shelf content addressed data layer, with associated libraries, documentation and tooling.
Background Information (Optional)
In order to understand the pieces that make up a CID and the IPLD model, you will need to understand the following fundamental concepts:
Base Encoding – This is the basically the way that binary data is converted into a compressed set of characters. For example, Base 10 encoding says that 0001 1010 = 26, but in base64 0001 1010 == MDAwMSAxMDEw. Play around with different encoding here
Hashing – A hash is a function that converts one value to another. In cryptography, the function that converts data from one form to another is an unknown process that is so complex it is impossible(?) to reverse, that produces a unique, fixed length output.
Codecs – Codecs are encoder/ decoder tools that translate to and from binary formats, in different ways.
Varints – Variable length integers, or Varints, are a way of compressing down integers into a smaller space than is normally needed. Since smaller numbers don't need as many bytes to represent them (0000 0010 == 2) vs (1110 0011 == 27), you can add a byte at the beginning to indicate how many bits are needed, to save on bit usage.
CIDs (Content Identifiers) – A CID is a binary address format that prepend a bunch of varints which self-describe the inner structure. A CID has a few parts; the hash, a description of the hash, a description of the encoding format, and a single int (1) to represent “CIDv1”
IPLD as Leverage
Treating the data layer as a discrete system provides leverage to content addressed developers:
How can we scale the size and complexity of the data that we share peer to peer?
Can we unify disparate content addressed formats and link between them? Git, blockchains, IPFS, etc.
Can we build distributed data structures that we can interact with like we do with hosted databases, while taking advantage of the benefits of content addressing?
How is IPLD related to IPFS?
IPLD is the data layer of IPFS. But the reverse is also true because IPFS is a block store for IPLD.
IPLD deals with data consistency, data addressing, data relationships (graphs), content addressed data structures, data navigation and more.
IPLD is generally not concerned about data storage or transports (with some caveats).
IPLD does not limit itself to peer to peer systems (Amazon S3 can be a perfectly reasonable IPLD block storage system!), but in general we think peer to peer is preferable!
IPLD and File Data
At its most fundamental, IPFS is a collection of:
Binary blobs of data - "blocks"
Their associated content identifiers - CIDs
These are both the core concerns of IPLD. IPFS builds on these primitives to provide a sophsticated peer to peer content addressing data stack, with a mature suite of tooling to deal with files.
Only the smallest files in IPFS are stored as a single blob ("block"): to keep block size practical, files are split up into chunks and spread across multiple blocks and linked together into a single graph.
Directories are graphs of named links pointing to files, forming graphs that address other graphs
Tutorials
For those who are newer to the world of Filecoin, Web3, and storage verification, check out the Protoschool tutorials. Tutorials you should complete include:
Follow along with this activity in the CLI that will help you understand the Merkle DAG structure, Merkle Roots, and the UnixFS file format
Further Introductory Reading:
Links
IPFS | Docs | GitHub - IPLD | Docs | GitHub - libp2p | Docs | GitHub - Filecoin | Docs | GitHub
Last updated
