Should use base32 as default in the "ipfs add -q --only-hash" command

[danimesq]

Instead, its outdated and still using CIDv0.

[danimesq]

@Stebalien

[aschmahmann]

This isn't a bug and is covered in the issue for the migration from CIDv0 to (b32) CIDv1 #5358.

[danimesq]

@aschmahmann what is the workaround to get the base32 hash of an file?

[danimesq]

Conclusion:

Ok, the pipelines command to get the CIDv1 of an file is: ipfs add -q --only-hash <file.extension> | ipfs cid base32

via: #5358 (comment)

[danimesq]

@aschmahmann when this workaround will be implemented in the ipfs add -q --only-hash command?

As newer applications should support CIDv1, some commands should be updated to default into it.

[danimesq]

@lidel, will this command be updated to use CIDv1 by default?

[lidel]

@DaniellMesquita you can opt-in to using CIDv1 at the time of file import by passing: ipfs add --cid-version 1

Note that defaulting to CIDv1 via --cid-version 1 implies --raw-leaves=true, which will produce different DAG than --raw-leaves=true, which is the default for CIDv0. We are still trying to find good time to make the switch, ideally will group all changes of the defaults like this into a single release.

For now, just pass --cid-version 1, it will save you the conversion step.

[danimesq]

@lidel, So, its ipfs add -q --cid-version 1 --only-hash?

Is it bad to produce an different merkletree/DAG? Then, how to keep compatibility?