Are we IPFS yet?

Where are we at?

The following table details how far along the ecosystem as a whole is in supporting the suite of InterPlanetary File System (IPFS) functionality. Note that we're using conformance tests from the official suite as a metric, since it's the best objective measure we are aware of.

If you have made progress in any of the yellow or gray items below, or simply want to offer a correction, please let us know.

Feature	IPFS	HTTP	Conformance Tests
Pubsub	Yes	Yes	25/25 tests passing
Swarm	Yes	Yes	13/13 tests passing
Refs	Yes	Yes	21/21 tests passing
Cat	Yes	Yes	14/14 tests passing
Get	Yes	Yes	9/9 tests passing
Version	Yes	Yes	1/2 tests passing
ID	Yes	Yes	1/2 tests passing
Bitswap	Partial (comparable to go-ipfs 0.4)	Yes	9/9 tests passing
Add	No	Yes	10/27 tests passing
Pin	Initial	No	10/16 tests passing
Block	Yes	Yes	25/27 tests passing
Dag	Yes	Yes	25/32 tests passing
DHT	Partial	Partial	13/20 tests passing

Remaining Work

The table below details the features that still need attention. This is a great opportunity for contributors who want to make a difference. See the projects list below for places to contribute.

Feature	IPFS	HTTP
Bootstrap	No	No
Name	No	No
Ping	No	No
Key	No	No
Config	No	No
Stats	No	No
Files	No	No

Feature

IPFS

HTTP

Bootstrap

Name

Ping

Key

Config

Stats

Files

Ecosystem Projects

rust-ipfs is an implementation that focuses on the suite of conformance tests provided by Protocol Labs

rust-ipfs-api - A HTTP client for an existing go-ipfs or js-ipfs node. Supports both hyper and actix

ipfs-embed - A light client implementation with a sled backend

rust-ipld - Basic rust ipld library supporting dag-cbor, dag-json and dag-pb formats

PolkaX's own rust-ipfs

Parity's rust-libp2p, which does a lot of the heavy lifting here