RFC: How to handle CIDv0 as we migrate to CIDV1

[kevina]

How should we handle existing CIDv0 as we migrate to CIDv1?

Some issues:

• Should pins be normalized to CIDv1
  • @whyrusleeping thinks so and I tend to agree
• Should we automatically convert CIDv0 to CIDv1 is display
  • @kevina think this might be a good idea in higher level commands such as ipfs add and ipfs ls, but lower level command such as ipfs dag and ipfs object CIDs should be left alone. In any case this should be controllable be a command line flag. @Stebalien also things so so I am assuming this is a yes.
• Should ipfs add default to full CIDv1 when raw leaves or not used or should it keep the internal links as CidV0 and just return a CidV1 for the root. The reason we might want to do this is because we put a lot of weight on keeping hashes the same.
  • The concurrences seams to be that we should keep internal links using CidV0 as default, at least for now

@whyrusleeping @diasdavid I know you both had thoughts on this. When you get a chance could you write down what you had in mind in the commends so we are all on the same page.

@Stebalien, others, general feedback is welcome.