Tell users that you can't make a CARv1 without a proper CID and let them figure out what to do
Document one potential hack for use-cases where a root CID is difficult or impossible (streaming data where you don't know roots up-front)
Fix go-car to accept zero roots but leave the caveat in this document that there may be use-cases in the wild where the assumption of >1 root is in-built.
I've done option 2 here, but it really just puts you in the position of having to accept another trade-off in that there may be applications using CAR files that assume the CID makes sense so this could break something else! So I'm now wondering if it'd just be easier and more sensible to wind back go-car's limitation to allow an empty root array.
We have 3 options here:
I've done option 2 here, but it really just puts you in the position of having to accept another trade-off in that there may be applications using CAR files that assume the CID makes sense so this could break something else! So I'm now wondering if it'd just be easier and more sensible to wind back go-car's limitation to allow an empty root array.
Thoughts?