Skip to content

Conversation

dannyob
Copy link
Contributor

@dannyob dannyob commented Aug 28, 2025

It took me a moment to realise that this was possible, so wanted to save that moment for future generations of IPFS newbies.

Describe your changes

Just an extra line in the docs explicitly showing how to use ipfs cid format -v 0.

Files changed

  • docs/concepts/content-addressing.md

Does this update depend on any other PRs?

nope!

Checklist before requesting a review

  • Passing the beta version of the Check Markdown links for modified files check. Action results can be viewed here.

Checklist before merging

  • Passing all required checks (The beta Check Markdown links for modified files check is not required)

It took me a moment to realise that this was possible, so wanted to save that moment for future generations of IPFS newbies.
Copy link

welcome bot commented Aug 28, 2025

Thank you for submitting this PR!
A maintainer will be here shortly to review it.
We are super grateful, but we are also overloaded! Help us by making sure that:

  • The context for this PR is clear, with relevant discussion, decisions and stakeholders linked/mentioned.
  • Your contribution itself is clear (grammar and spelling checked, any code blocks checked and commented) and in its best form. Follow the docs contribution guidelines if they apply.

Getting other community members to do a review would be great help too on complex PRs (you can ask in the chats/forums). If you are unsure about something, just leave us a comment.
Next steps:

  • A maintainer will triage and assign priority to this PR, commenting on any missing things and potentially assigning a reviewer for high priority items.
  • The PR gets reviews, discussed and approvals as needed.
  • The PR is merged by maintainers when it has been approved and comments addressed.

We currently aim to provide initial feedback/triaging within two business days. Please keep an eye on any labelling actions, as these will indicate priorities and status of your contribution.
We are very grateful for your contribution!

gammazero and others added 4 commits September 25, 2025 11:02
add explicit note that conversion from CIDv1 to CIDv0 only works
when the CIDv1 uses dag-pb codec, as CIDv0 only supports dag-pb
Copy link
Member

@lidel lidel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @dannyob

Caveat: conversion from CIDv1 to CIDv0 is only possible when the CIDv1 uses the dag-pb codec (0x70), as CIDv0 only supports dag-pb. CIDs using other codecs like raw (0x55), dag-cbor (0x71), or dag-json (0x0129) cannot be converted to CIDv0. Added this clarification.

Copy link
Contributor

🚀 Build Preview on IPFS ready

@lidel lidel changed the title Make explicit that you can use ipfs cid format to convert both ways docs: make explicit that you can use ipfs cid format to convert both ways Sep 25, 2025
@lidel lidel merged commit a40b064 into ipfs:main Sep 25, 2025
4 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants