Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update IPFS Kubo to 0.20.0 #30652

Closed
lidel opened this issue May 29, 2023 · 0 comments · Fixed by brave/brave-core-crx-packager#630
Closed

Update IPFS Kubo to 0.20.0 #30652

lidel opened this issue May 29, 2023 · 0 comments · Fixed by brave/brave-core-crx-packager#630
Assignees

Comments

@lidel
Copy link

lidel commented May 29, 2023

cc @cypt4 @bbondy @autonome

Signed Binaries: https://dist.ipfs.tech/kubo/v0.20.0/
Release Notes: https://github.com/ipfs/kubo/blob/master/docs/changelogs/v0.20.md

This release includes internal refactoring and bugfixes,
but there should be no impact on features exposed by Brave aside from --empty-repo described below.

--empty-repo is now the default

When initializing a repository with ipfs init, --empty-repo=true is now the default.

This means that the repository will be empty by default, instead of containing the introduction README files.
More about the rationale behind this decision on the tracking issue.

@cypt4 I am mentioning this just in case you ended up counting the number of pins user has to detect if they did any NFT pinning. 👉 If you assumed the number needs to be bigger than 2 recursive pins, read below.


To make this work with both old and new nodes, you can take a look at the "before and after summary here.

If you want to count user pins, and want to make it work for both old and new repositories,
simply filter out below two CIDs before producing the number of user pins:

$ ipfs pin ls -t recursive
QmQPeNsJPyVWPFDVHb77w8G42Fvo15z4bG2X8D2GhfbSXc recursive # README dir (always pinned before Kubo 0.20)
QmUNLLsPACCz1vLxQVkXqqLX5R1X345qqfHbsf67hvA3Nn recursive # always pinned empty dir 
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants