Shipyard winds down IPFS work after Protocol Labs ends funding
Reported by Cointelegraph · AI-assisted summary by ChikoCorp AI News Desk
AI-generated summary based on the linked source; not independently verified. This is not investment advice. Verify market-moving details at the original publisher before acting. See our editorial policy, AI content policy, and financial disclaimer.
Summary
Shipyard, the maintainer of the InterPlanetary File System (IPFS), will cease its engineering, maintenance, and infrastructure operations on September 30 after Protocol Labs chose not to renew its funding. This will leave several IPFS projects such as Kubo, Helia, Boxo, Rainbow, IPFS Desktop, and IPFS Companion without dedicated maintainers. Protocol Labs will retain ownership of IPFS-related domains and infrastructure and decide their future use.
Why it matters
The source signals that while IPFS itself will continue, the withdrawal of Shipyard’s dedicated stewardship may impact the maintenance and development of popular IPFS implementations and services. Protocol Labs plans to support IPFS development through lighter stewardship via grants to individual maintainers, indicating a shift in how the protocol's ecosystem will be managed.
Key context
IPFS is an open-source peer-to-peer protocol for decentralized data storage and sharing, originally created by Protocol Labs, which also developed Filecoin. Shipyard was founded in 2024 by developers formerly at Protocol Labs to independently maintain IPFS projects. The wind-down affects public infrastructure nodes and gateways currently operated by Shipyard, though IPFS as a whole will not shut down.
Key numbers and entities
Organizations: Shipyard, Protocol Labs, IPFS Foundation Individuals: Molly Mackinlay (Protocol Labs engineering and research lead) Projects affected: Kubo, Helia, Boxo, Rainbow, IPFS Desktop, IPFS Companion Infrastructure: ipfs.io, dweb.link, delegated-ipfs.dev, IPFS bootstrap nodes Date: Shipyard operations end September 30, 2024
What remains unclear
The source does not specify who might take over maintenance of the affected projects or the precise timeline and scope of Protocol Labs’ future involvement with IPFS infrastructure. The long-term implications for IPFS users and the broader ecosystem beyond Protocol Labs’ grant program are also undetailed.