Kubo 0.40 is out! 🎉
🔢 IPIP-499: CID Profiles for reproducible imports
🔀 IPIP-523 + IPIP-524: Gateway format handling
🧹 Flatfs auto-cleans interrupted imports
🚇 P2P tunnels and AutoNATv2
🛠️ CLI and WebUI improvements
🐹 Go 1.26 and more!
github.com/ipfs/kubo/releases/tag/v0.40.0
ICYMI, ProbeLab has launched a brand new website to showcase the metrics we're publishing for @ipfs.tech, @ethereum.bsky.social, @filecoin.bsky.social, @polkadot.bsky.social, Gnosis, Celestia, Optimism, Base, Avail, with several more coming soon! Head to: probelab.io to see what's new!
You can finally self-host IPFS at home 🏠✨
Major updates to Kubo, Boxo, and Helia.
DHT Provide Sweep, AutoTLS, HTTP retrieval.
Here's everything we shipped in 2025:
ipshipyard.com/blog/2025-sh...
We published a blog post explaining how Provide Sweep enables self-hosted Kubo nodes to reliably advertise millions of CIDs to the Amino DHT with smooth, predictable resource usage.
Now default in Kubo v0.39 after successful testing in v0.38.
ipshipyard.com/blog/2025-dh...
Upgrade your Kubo node!
The IPFS Amino DHT finally has a spec 🎉
specs.ipfs.tech/routing/kad-...
🚢 Kubo 0.38 is out!
🧹 Opt-in Sweeping DHT Provider handles CID announcements predictably with reduced resources
🚨 Gateway errors with retrieval diagnostics
🎨 WebUI v4.9 w/ Diagnostics screen
📌 Pin name and MFS fixes
⚙️ Simplified Provide config
github.com/ipfs/kubo/re...
Same experience here. Owned both and completely agree.
Shipped a cool demo showing map tiles served over IPFS! 🗺️
Why does this matter? Decentralized maps = no single point of failure, offline-first geographic data, and community-owned infrastructure
Zoom around bafkreiclsdmwsgzkitv5g2akcdxugrotppn3mcg6lzukcjyj5cj5aferfy.ipfs.dweb.link
Anyone looking to adopt a battle-tested TypeScript polyglot? 🐙
Ex-PayPal, Amazon, Protocol Labs — raised the bar at Amazon, led OSS with ~60k–100k+ MAU, and helped shape IPFS & libp2p.
Looking for a fun, high-impact project to code, mentor, and keep pushing systems (and people) forward.
#adoptMe
One Redditor calls 0.36 "an amazingly huge improvement": www.reddit.com/r/ipfs/comme...
If your kubo node talks to the public network, it's probably worth the upgrade!
I recommend using Swiss Topo for planning hikes in Switzerland
🚀 Kubo v0.33.0 is out!
Highlights:
✨ Streamlined AutoTLS listener setup
🔄 Shared listeners between TCP & WebSocket transports
⚡️ New datastore options to improve writes with Pebble
🛠️ MFS stability improvements
🌐 New DoH resolvers for .eth and .crypto
🧰 WebRTC Direct fixes
github.com/ipfs/kubo/re...
Weekly Network Health Reports for the Filecoin DHT are now a thing - brought to you by @probelab.io!
Reports live on probelab.io - latest one is here: probelab.io/filecoin/dht... - and are produced weekly on Mondays.
Debugging retrievability of blocks by CID in @ipfs.tech is now easier!
Recent improvements to IPFS Check allow you to test retrievability with just a CID
Learn more 👇
www.youtube.com/watch?v=XeNO...
It may come as a surprise, but most @ethereum.bsky.social nodes are not on the big 3 cloud providers. Only 1003/8825 nodes are on AWS, 83/8825 on GCP, 50/8825 on Azure.
You can read about it in our weekly reports on @probelab.io
For this week's report on Ethereum: probelab.io/ethereum/dis...
CURL 8.4.0 released a couple days ago with IPFS URI support! A project that took well over 500 days from start to finish 😁 @ipfs.tech #ipfs #curl blog.ipfs.tech/ipfs-uri-sup...
DHT identifiers are bytes anyway. The different RPCs give context and disambiguate the identifiers 👍️
@expede.wtf what do you mean by "update CIDs"?If you want to use a generic libp2p DHT (without IPFS), you could just define a new RPC ("feature"), accepting CIDs as input. This sub-DHT would be totally isolated from IPFS (no common "feature"), but you could still use IPFS bootstrapers to join.
There is an ongoing discussion about creating a more stable and reliable sub-DHT https://github.com/ipfs/specs/issues/404
The Composable DHT won't make nodes more stable, but not less stable either. Stability depends on the stability of the evaluated "feature". However, if you need very reliable network, with long lived peers, you would be able to add a new "feature" creating a sub-DHT of very stable nodes.
I can only agree with @jorropo.net
It is opening new doors, and we still need to explore what it can enable. For instance, we could even make IPv4 and IPv6 "features", to allow all nodes to discover all peers they can connect to, and to allow content providers to advertise for both IPv4 and IPv6 clients.
We can imagine that each libp2p protocol can be seen as a distinct "feature". It would make it easier to discover, and talk only with nodes speaking your libp2p protocol
DHT "Protocols" represent sets of DHT "features" that a specific application is using. E.g the IPFS DHT "Protocol" is made up of the IPFS Provider Records, IPNS, and Hole Punching "features".
You can think of a "feature" like a RPC that is not essential for vanilla Kademalia to work, but useful to your application. E.g IPFS Provider Records can be seen as a "feature", because storing and serving IPFS data shouldn't be a requirement for all DHT nodes.
Link to the IPFS Thing 2023 recording on the Composable DHT https://www.youtube.com/watch?v=OHrtv1jz2Jc
