IPFS node implementation
ipfs is an early alpha level crate: APIs and their implementation are subject to change in
any upcoming release at least for now. The aim of the crate is to become a library-first
production ready implementation of an Ipfs node.
IPLD dag-json, dag-cbor and some dag-pb functionality.
IPNS functionality around
P2P handling for IPFS nodes.
Storage implementation(s) backing the
An Ipfs block consisting of a
A description of currently active connection.
The facade for the Ipfs node.
Ipfs node options used to configure the node to be created with
The (opaque) key of a record.
The ID of a single listener.
Representation of a Multiaddr.
A wrapper for
Identifier of a peer of the network.
Adaptation hopefully supporting somehow both Floodsub and Gossipsub Messages in the future
Stream of a pubsub messages. Implements
In-memory testing configuration used in tests.
Default node configuration, currently with persistent block store and data store for pins.
Configured Ipfs which can only be started.
Represents the result of a Kademlia query.
Identity keypair of a node.
The public key of a node's identity keypair.
A quorum w.r.t. the configured replication factor specifies the minimum number of distinct nodes that must be successfully contacted in order for a query to succeed.
Represents the configuration of the Ipfs node, its backing blockstore and datastore.
A CID with the default Multihash code table