AIBRIEF
IPFS, the peer to peer protocol behind much of the decentralized web, is losing a key maintainer team on September 30, 2026, after Protocol Labs declined to renew Shipyard's funding.
IPFS, the peer-to-peer file-sharing protocol behind much of the decentralized web, will lose a major maintainer team on September 30, 2026, when Shipyard ends three years of work on the ecosystem. The shutdown follows Protocol Labs' decision not to renew Shipyard's funding, the company said.
Shipyard, funded by Protocol Labs for more than two years, maintains the reference implementations and tooling other IPFS developers build on: Kubo (the Go implementation), Helia (the JavaScript version), Boxo, Rainbow, IPFS Desktop, IPFS Companion, Someguy, the Service Worker Gateway, and IPFS Check. It also contributes to the underlying networking libraries go-libp2p and js-libp2p.
The protocol itself is not ending. Shipyard says a follow-up post will detail shipped engineering work, including inbrowser.link (a tool for fetching and verifying websites and downloads directly in the browser) and a re-architected gateway stack it says handles about 3× more traffic while cutting operating costs by around 80%. Plans for HTTP-native IPFS, sustainable content routing, support for large SHA-256 objects, and Tor-based pseudonymous hosting are on hold.
The open question is who, if anyone, picks up maintenance, and on what timeline. Hacker News commenters point to Iroh, a newer p2p stack from ex-Protocol Labs engineers, and to Reticulum, a general-purpose alternative. Neither is a drop-in replacement for the Kubo-and-Helia world Shipyard is leaving.