1 unstable release

0.1.0 Dec 28, 2022

#41 in #dag

MPL-2.0 license

576 lines


Async DAG library generic over Node type, Node Identifier Type and Backend (storage of the DAG).


Experimental. Do not use.

What is this?

My Problem was, that I wanted to implement a DAG on IPFS/IPLD. The Problem, though, is that the existing IPFS/IPLD libraries do not feature functionality to build a DAG easily. There are libraries for DAGs, but they all implemented the storage functionality themselves. I needed a backend that is async and generic, so that I can use IPFS (or anything else that works async) in the backend. So this lib was born.

This library does define a simple interface for the underlying backend:

pub trait DagBackend<Id, N>
    where N: Node,
          Id: NodeId + Send
    async fn get(&self, id: Id) -> Result<Option<N>>;
    async fn put(&mut self, node: N) -> Result<Id>;

and that's it. The AsyncDag type implements the DAG data structure on top of that.


Because this library was initialized to be used with IPFS in the backend, is has some limitations:

  • It does assume that you cannot ever delete nodes. You can rewrite the DAG, but this does not necessarily delete nodes.

This list will be extended in the future. Do not assume it is complete!




~34K SLoC