For #85 (comment) and #35 (comment), we need to run an ipfs node that understand to read and write Namespace Merkle Tree (tree)nodes. The latter will be achieved by a IPLD plugin for a NMT.
To communicate with the node, we can either use go-ipfs-api or, try to directly get the API object from a config and environment (basically what the ipfs commands do, e.g. see DagGetCmd). The latter might have the advantage of having slightly more control over how to insert the nodes in the ipld dag.
Either way, it would be ideal if the user can configure which node to use.
For #85 (comment) and #35 (comment), we need to run an ipfs node that understand to read and write Namespace Merkle Tree (tree)nodes. The latter will be achieved by a IPLD plugin for a NMT.
To communicate with the node, we can either use go-ipfs-api or, try to directly get the API object from a config and environment (basically what the ipfs commands do, e.g. see DagGetCmd). The latter might have the advantage of having slightly more control over how to insert the nodes in the ipld dag.
Either way, it would be ideal if the user can configure which node to use.