Shipyard, a development team in the IPFS ecosystem, said it will stop IPFS-related engineering, maintenance, and infrastructure operations on Sept. 30 after Protocol Labs decided not to renew its funding. The change leaves several core projects maintained by Shipyard — including Kubo, Helia, and IPFS Desktop — without dedicated maintainers, based on the team’s announcement. Shipyard also said the future of public infrastructure such as ipfs.io and dweb.link, along with IPFS bootstrap nodes, will be decided by Protocol Labs. The team added that it will help with the transition through the end of September. The announcement outlines a shift in responsibility across parts of the IPFS stack and public services currently tied to Shipyard’s work.
Shipyard, a development team in the IPFS ecosystem, said it will stop IPFS-related engineering, maintenance, and infrastructure operations on Sept. 30 after Protocol Labs decided not to renew its funding.
Projects and services affected
Once Shipyard ends those operations, core projects it has maintained — including Kubo, Helia, and IPFS Desktop — will no longer have dedicated maintainers. Shipyard said the future of public infrastructure such as ipfs.io and dweb.link, as well as IPFS bootstrap nodes, will be determined by Protocol Labs.
Transition timeline
Shipyard said it will assist with the transition through the end of September.
This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan. Disclaimer:
The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.
Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.
