--raw-leaves leads to base32 and base58 mixed outputs

[hsanjuan]

Version information: master

Description:

Probably --raw-leaves should not return base32 cids if the user did not select them. What I'm more worried about is that some outputs (adding with wrapping folders, refs -r...) may contain V0 cids with base58 and V1 cids with base32 all mixed regardless of user choice which is bad UI.

$ ipfs add --raw-leaves -Q bigfile.bin 
QmQnNC6QxkAuzAU8pejigkzNxUVGV9W8VvG6qKN1jh8i8M
$ ipfs add --raw-leaves -Q smallfile.bin  
bafkreigga22iwqldlydhd2bui4dbfowa3jjhdnrocvetm254k3blegqz5a

Feel free to close if this is not actionable (should auto-fix whenever we switch to V1 cids by default). Just wanted to bring it up and --raw-leaves are experimental anyways. Fixing this is probably just going to add more boilerplate.

[Stebalien]

I mean... I'm tempted to just say "CIDv1 on raw leaves FTW!". I'm not sure why we didn't go with that in the first place. Unfortunately, that would make a bunch of people very unhappy (I think?).

Actually, @parkan, is what flags are the Internet Archive using? Are they using CIDv1 by default? --raw-leaves is experimental so I'm fine changing the defaults if it doesn't break any known users.

[lidel]

I think this can be closed now that some standardization in form of IPIP-499 landed in:

• Implement modern CID profile from IPIP-499 #11071

should auto-fix whenever we switch to V1 cids by default.

We now have Import.* configuration that controls implicit defaults, likely removing the papercut of having to pass options to every ipfs add.

Mixed import can be avoided by setting Import.CidVersion=1 + explicit/implicit Import.UnixFSRawLeaves=true (or to follow IPIP-499 profile, ipfs config profile apply unixfs-v1-2025). Once done, all output uses CIDv1 consistently -- both file roots and leaf nodes. No more mixed encodings.