For metadata, eula and terms documents, we currently only support IPFS mutlihashes, as in
* to a ZIP archive file with market documents.
* @param meta The XBR market metadata published by the market owner. IPFS Multihash pointing
* to a RDF/Turtle file with market metadata.
In addition to IPFS, we should also support plain HTTP URLs pointing to files.
actually, nothing in the on-chain contracts checks for the supplied strings being an actual multihash .. and I'm not sure if we should check anything - changing title/labels accordingly
For metadata, eula and terms documents, we currently only support IPFS mutlihashes, as in
In addition to IPFS, we should also support plain HTTP URLs pointing to files.