Doctorcrypto About RSS Subscribe
Doctorcrypto
HomeBusiness › Shipyard winds down IPFS work after Protocol Labs ends funding
Business

Shipyard winds down IPFS work after Protocol Labs ends funding

By Diego Whitfield · · 2 min read

Ipfs Shipyard, the group behind much of the development around the InterPlanetary File System, is scaling back its operations after Protocol Labs cut off its funding, leaving core software components without dedicated maintainers and raising questions about the future of public services central to the decentralized web protocol.

A Funding Cliff Hits Core Development

The decision to end financial support has effectively stranded key parts of the IPFS ecosystem. Without a dedicated team maintaining the software, essential tools and libraries risk falling into disrepair, a concern for the developers and projects that rely on the protocol to store and share data across a distributed network.

IPFS underpins a range of decentralized applications, from Web3 platforms to NFT storage solutions, making the stability of its underlying software a matter of concern beyond just the immediate maintainers. When funding evaporates, the burden of keeping critical infrastructure alive often shifts to volunteers or falls away entirely.

When the money dries up, open-source infrastructure can quietly crumble beneath the applications that depend on it.

Public Services in Question

Perhaps the most pressing consequence is what happens to the public-facing services that Shipyard helped keep running. With the group winding down, responsibility for those offerings now rests largely with Protocol Labs, the organization that originally created IPFS and had been bankrolling the maintenance work.

The situation illustrates a recurring tension in the crypto and Web3 space, where ambitious decentralized protocols still lean heavily on centralized funding sources to survive. Losing a single backer can jeopardize tools meant to be resilient and community-owned.

Key concerns emerging from the wind-down include:

  • The absence of dedicated maintainers for core IPFS software
  • Uncertainty over the continuity of widely used public services
  • Increased reliance on Protocol Labs to fill the gap

What Comes Next

For now, the future of the affected software and services hinges on whether Protocol Labs steps in to sustain them or whether the broader community can rally to fill the void. The episode serves as a reminder that even foundational pieces of decentralized technology remain vulnerable to shifting funding priorities, and that the promise of a truly distributed web often collides with the economics of who pays to keep it working.

Was this useful?👍 Yes👎 No