Shipyard said on August 24, 2026, that it would wind down its engineering, maintenance and infrastructure work connected to the InterPlanetary File System after Protocol Labs declined to renew the team’s funding. Shipyard set September 30, 2026, as the final day for its IPFS-related work and said it would use the intervening weeks to assist people who depend on its software and services.
The announcement concerns Shipyard’s role in the IPFS ecosystem, not the termination of the IPFS protocol itself. The team said Protocol Labs had supported its work for more than two years, and described the loss of that funding as the direct reason for ending operations in this area. An update added to the post on August 25 pointed readers to a separate statement from Protocol Labs about its future plans, but the contents of that statement were not included in the supplied evidence.
Shipyard said it had spent roughly three years working on the broader ecosystem. Its plans had included simpler implementations designed around HTTP, more durable content routing, support for large objects using native SHA-256 hashes, and pseudonymous hosting and retrieval through Tor and onion services. The team said it would not be able to carry those efforts forward itself.
The group did not provide a complete inventory of affected components or infrastructure in the available announcement. It nevertheless warned that the consequences extend beyond the organization and invited maintainers, infrastructure operators and users of its work to make contact before the end of September. Shipyard offered to answer questions, supply context and support transition work where reasonably possible.
That transition window is important because open protocols can depend on concentrated maintenance even when their code and specifications remain publicly available. Responsibility for individual packages, network services or experiments may need to move to other organizations or community contributors. The announcement does not identify confirmed successors, new funding or a schedule for transferring particular projects, leaving operators to determine their own dependencies and seek details directly from the team.
Shipyard also referenced work intended to make IPFS function more smoothly on the web, including a public-gateway transition in which direct navigation routes through a verifiable service-worker gateway and support for verifiable ENS resolution. However, the post primarily serves as a notice of the funding decision and approaching end date, rather than a technical migration guide.
For IPFS users, the immediate issue is therefore narrower but still material: Shipyard’s maintenance and infrastructure contribution is scheduled to stop after September 30. The protocol’s wider direction cannot be determined from Shipyard’s statement alone. Until affected repositories and services are specified, maintainers and operators relying on the team’s work will need to use the offered transition period to establish what changes for their deployments.
