You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IPFS will soon switch to CIDv1 by default (bafy.....) vs the old CIDv0 (Qm.....):
If you can't decide between CIDv0 and CIDv1, consider choosing CIDv1 for your new project and opt in by passing a version flag (ipfs add --cid-version 1). This is more future-proof and safe for use in browser contexts.
The IPFS project will switch to CIDv1 as the new default in the near future.
As there's no downside using CIDv1 - and converting existing CIDv0 to CIDv1 in any output git-lfs-ipfs makes, like ipfs does when you set --upgrade-cidv0-in-output - the change should be a no-brainer.
The text was updated successfully, but these errors were encountered:
IPFS will soon switch to CIDv1 by default (bafy.....) vs the old CIDv0 (Qm.....):
Source
They are much better to handle, as they are not case sensitive. So using them in directly in the browser with
ipfs://
works.As there's no downside using CIDv1 - and converting existing CIDv0 to CIDv1 in any output git-lfs-ipfs makes, like ipfs does when you set
--upgrade-cidv0-in-output
- the change should be a no-brainer.The text was updated successfully, but these errors were encountered: