IPFS Maintainers Winding Down
- ID
- 17379
- Status
- summarized
- Published
- 24 Aug 2026, 11:48 PM
- Fetched
- 25 Aug 2026, 4:07 AM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://ipshipyard.com/blog/2026-the-end-of-ipfs-at-shipyard/
- Source URL
- https://hnrss.org/best
Summary
- Score
- 6.5
- Created
- 25 Aug 2026, 4:08 AM
- Tags
- Audience
- developersdatabase_learnerssaas_founders
What happened
Protocol Labs will not renew funding for Shipyard, the team maintaining core IPFS infrastructure and libraries. Shipyard's final day of IPFS work is September 30, 2026, after which projects including Kubo, Helia, Boxo, Rainbow, IPFS Desktop, and IPFS Companion will lose dedicated maintainers, and public infrastructure such as ipfs.io, dweb.link, and IPFS bootstrap nodes will cease operation under Shipyard.
Why it matters
If you ship anything that depends on IPFS gateways, bootstrap nodes, or core libraries (Kubo, Helia, Boxo), you need a migration or self-hosting plan before October 2026. Protocol Labs owns the domains and will decide their fate, but there is no guarantee of continuity. Projects using IPFS for decentralized file storage, NFT metadata, or verifiable downloads should evaluate alternatives like Arweave, Filecoin direct deals, or centralized CDN fallbacks now rather than waiting for the transition.
Discussion angle
Which IPFS dependencies in your stack are actually load-bearing versus nice-to-have, and what's the cheapest fallback if ipfs.io and dweb.link go dark or degrade?