
TL;DR
Shipyard will cease its IPFS-related operations by September 30, 2026, following the decision by Protocol Labs not to renew funding. This marks a significant shift in the IPFS ecosystem, impacting ongoing projects and user support.
✦ Why It Matters
Consider exploring alternative funding or support options for ongoing IPFS projects to ensure continuity.
Key Takeaways
Full Summary
Shipyard, a key player in the InterPlanetary File System (IPFS) community, has announced it will wind down its operations due to the non-renewal of funding from Protocol Labs. Over the past three years, Shipyard contributed significantly to the IPFS ecosystem, including the development of inbrowser.link for verifiable web content and a re-architected IPFS gateway that increased traffic capacity by three times while cutting costs by 80%.
Their work also included simplifying IPFS deployment through HTTP-native approaches. With the funding cut, Shipyard will stop maintaining critical projects like Kubo and IPFS Desktop, and will cease contributions to upstream projects like go-libp2p.
The shutdown will affect public infrastructure services such as ipfs.io and dweb.link, leaving the future of these services uncertain. Shipyard aims to assist in the transition until their final day of operations.
Related