When the Shipyard Sinks: IPFS Faces Its Governance Crossroads

On September 30, the Shipyard team—the quiet engine behind IPFS’s core implementations—will dissolve. No dramatic fork, no hostile takeover. Just a funding cut by Protocol Labs, and a handful of the most experienced maintainers of Kubo, Helia, Boxo, Rainbow, and IPFS Desktop will walk away. People often ask me, as a DAO governance architect, what keeps me up at night. It’s not the code. Code is law, but people are the soul. And when the soul of a critical infrastructure layer like IPFS loses its dedicated caretakers, the law of the network starts to bend. Let’s pull back the curtain. IPFS is not a single blockchain; it’s a protocol, a content-addressed file system that underpins everything from NFT metadata to Filecoin’s storage deals. For years, the Shipyard team—veterans who had built the protocol at Protocol Labs—were the ones who fixed bugs, reviewed pull requests, kept the bootstrap nodes alive, and ensured that the dweb.link gateway didn’t go dark. They were a small, focused group, but they were the difference between a stable, evolving protocol and a stagnant one. Their work was invisible to most users, but it was the bedrock of the decentralized web’s promise. Now, that bedrock is cracking. Protocol Labs has decided not to renew Shipyard’s funding, citing a shift to a “lighter-weight governance model.” Instead of a centralized team, the IPFS Foundation will distribute grants to individual maintainers. On paper, this sounds like a move toward true decentralization—cutting the cord from a single corporate backer. But in practice, it’s a gamble. I’ve seen this movie before. In 2017, during the ICO boom, I wrote “The Ethics of Empty Vests” after auditing 50 whitepapers that promised decentralization but delivered nothing but vapor. The pattern is always the same: when the money dries up, the maintainers leave, and the community is left to pick up the pieces. The difference here is that IPFS is not a scam; it’s a real, battle-tested protocol. But the risk is real. Let me be clear: the protocol itself won’t stop working. The IPFS network is a distributed system of independent nodes. But the software that runs those nodes—Kubo, Helia, Boxo—will no longer have dedicated engineers triaging issues. Security patches will slow down. Compatibility with evolving browser APIs will lag. The bootstrap nodes that new peers rely on to join the network? They’re shutting down too. The immediate effect is a technical debt avalanche. The medium-term effect is a loss of trust. And the long-term effect? That depends on whether the community can step up. This is where the contrarian angle comes in. Perhaps this is exactly what decentralization needs. The Shipyard team was a luxury—a central point of failure dressed in the clothes of a decentralized protocol. By cutting that cord, Protocol Labs is forcing the IPFS ecosystem to evolve from a project managed by a benevolent lab to a truly community-owned infrastructure. The IPFS Foundation’s idea of funding individual maintainers is not new; it’s how the Linux kernel survived for decades. But the transition is brutal. There will be a gap—a “maintenance vacuum” between the end of the Shipyard contract and the time when the Foundation’s new grant system is fully operational. During that gap, bugs will pile up, and if a critical vulnerability is discovered, the response time could be measured in weeks, not hours. I’ve been through this before. In 2020, during DeFi Summer, I started a “DAO Literacy” workshop series in Paris because I saw the gap between developers and users. The same gap exists here. The developers who rely on IPFS—the NFT platforms, the storage providers, the dApp builders—need to understand that they can’t just consume. They need to contribute. The “govern the entrance, not the exit” principle applies here: instead of worrying about who controls the protocol, we should focus on who maintains the entrance—the code, the documentation, the community support. If the IPFS ecosystem treats this as a wake-up call to build a self-sustaining contributor base, it could emerge stronger. If it waits for another lab to save it, it will wither. Let me ground this in my own experience. In 2021, I co-founded “SoulBound Stories,” a platform for non-transferable digital identities tied to real-world contributions. We raised €150,000 from community grants, not VCs, because we wanted to remain independent. The lesson was simple: funding models shape governance. Shipyard’s closure is a test of whether IPFS can survive without a corporate patron. The answer will come from the community. Are there enough people willing to maintain Kubo in their spare time? Will the Filecoin miners who depend on Kubo step up to fund its development? Or will we see a fork—a community-led version of Kubo that diverges from the official implementation? That fragmentation could be the worst outcome, because it would split the developer mindshare and confuse users. I’m not a pessimist by nature. I’ve seen the power of decentralized communities to heal themselves. During the 2022 bear market, I started “The Blockchain Anchor,” a free mentorship program that helped over 500 people navigate the crash. The human spirit, when aligned with shared values, can overcome even the most broken funding models. IPFS is more than a protocol; it’s a vision of a web where files are not owned by gatekeepers. To preserve that vision, we need to move from passive consumption to active stewardship. The Shipyard team’s departure is not a death knell. It’s a call to arms. So what now? Watch the IPFS Foundation’s next moves. If they announce a clear grant program for Kubo maintainers within the next 30 days, the risk is manageable. If they stumble, the community must organize. I’ll be watching the GitHub commit frequency, the security advisory log, and the discussions in the IPFS forums. I’ll also be writing—because as an evangelist, my job is to translate the technical into the human. Code is law, but people are the soul. The soul of IPFS is about to be tested. Let’s see if the community is ready to carry the torch.