The core objects and interfaces of the interplanetary file system (IPFS)
C# Batchfile
Failed to load latest commit information.
.nuget chore(ci): build coverage report Oct 17, 2017
doc docs(core): more documentation Oct 27, 2017
src fix(NetworkProtocol): do not log registering Jul 15, 2018
test fix(MultiAddress): ipfs is an alias of p2p, fixes #60 Jul 1, 2018
tools/docfx chore(docfx): deploy docs to gh-pages Jan 11, 2017
.gitignore feat(compile): build debug and XML documentation file Oct 15, 2017
GitVersionConfig.yaml #7 use gitversion to generate semvar number Oct 16, 2015
IpfsCore.sln chore(ci): use travis Jan 22, 2018
IpfsCore.vsmdi Used bomremover for #11 Oct 18, 2015
LICENSE Initial commit Oct 13, 2015
Local.testsettings Used bomremover for #11 Oct 18, 2015 chore(ci): use travis Jan 22, 2018
TraceAndTestImpact.testsettings Used bomremover for #11 Oct 18, 2015


build status travis build Coverage Status Version docs

The core objects and interfaces of the IPFS (Inter Planetary File System) for .Net (C#, VB, F# etc.)

The interplanetary file system is the permanent web. It is a new hypermedia distribution protocol, addressed by content and identities. IPFS enables the creation of completely distributed applications. It aims to make the web faster, safer, and more open.

It supports the following runtimes

  • .NET Framework 4.5
  • .NET Standard 1.4
  • .NET Standard 2.0

More information is on the Documentation web site.

Getting started

Published releases of IPFS Core are available on NuGet. To install, run the following command in the Package Manager Console.

PM> Install-Package Ipfs.Core

For the latest build or older non-released builds see Continuous Integration.

Major objects

See the API Documentation for a list of all objects.


All hashes in IPFS are encoded with multihash, a self-describing hash format. The actual hash function used depends on security requirements. The cryptosystem of IPFS is upgradeable, meaning that as hash functions are broken, networks can shift to stronger hashes. There is no free lunch, as objects may need to be rehashed, or links duplicated. But ensuring that tools built do not assume a pre-defined length of hash digest means tools that work with today's hash functions will also work with tomorrows longer hash functions too.


A standard way to represent a networks address that supports multiple network protocols. It is represented as a series of tuples, a protocol code and an optional value. For example, an IPFS file at a sepcific address over ipv4 and tcp is


Merkle DAG

The DagNode is a directed acyclic graph whose edges are a DagLink. This means that links to objects can authenticate the objects themselves, and that every object contains a secure representation of its children.

Every Merkle is a directed acyclic graph (DAG) because each node is accessed via its name (the hash of DagNode). Each branch of Merkle is the hash of its local content (data and links); naming children by their hash instead of their full contents. So after creation there is no way to edit a DagNode. This prevents cycles (assuming there are no hash collisions) since one can not link the first created node to the last note to create the last reference.


Most binary data (objects) in IPFS is represented as a Base-58 string; the BitCoin alphabet is used.

Base58 is a group of binary-to-text encoding schemes used to represent large integers as alphanumeric text. It is similar to Base64 but has been modified to avoid both non-alphanumeric characters and letters which might look ambiguous when printed. It is therefore designed for human users who manually enter the data, copying from some visual source, but also allows easy copy and paste because a double-click will usually select the whole string.


Copyright © 2015-2018 Richard Schneider (

The IPFS Core library is licensed under the MIT license. Refere to the LICENSE file for more information.