Loading market data...
Cripto

Shipyard Winds Down IPFS Work as Protocol Labs Ends Funding

By GFdaily Newsroom
ShipyardIPFSProtocol Labsfunding cutdecentralized web
September 1, 2026 6 min de leitura
Shipyard Winds Down IPFS Work as Protocol Labs Ends Funding

Why the funding cut

->

Por que o corte de financiamento

or "Por que o financiamento foi cortado". I'll use "Por que o corte de financiamento" but better: "Por que o financiamento foi cortado" but the heading is short. I'll use "Por que o corte de financiamento" but it's a bit awkward. Actually "Por que o corte de financiamento?" is fine. Or "Motivo do corte de financiamento". I'll go with "Por que o corte de financiamento" as it's direct. Then paragraph:

The move means Shipyard will no longer be building on IPFS, a peer-to-peer protocol designed to make web content faster and more decentralized. Protocol Labs has been the financial engine behind much of IPFS development, and with that support ending, Shipyard has no reason to keep the projects alive. The company did not say whether any of the work will be finished or handed off to other teams.

Translation:

A medida significa que a Shipyard não construirá mais no IPFS, um protocolo ponto a ponto (peer-to-peer) projetado para tornar o conteúdo da web mais rápido e mais descentralizado. A Protocol Labs tem sido o motor financeiro por trás de grande parte do desenvolvimento do IPFS e, com o fim desse apoio, a Shipyard não tem motivos para manter os projetos vivos. A empresa não informou se algum dos trabalhos será concluído ou repassado a outras equipes.

Note: "peer-to-peer" can be "ponto a ponto" but I'll keep "peer-to-peer" in parentheses or just use "ponto a ponto". I'll use "ponto a ponto (peer-to-peer)" to be clear. Next:

IPFS loses a development partner

->

IPFS perde um parceiro de desenvolvimento

Paragraph:

IPFS is an open-source project, but open source doesn't mean free to build. Contributions rely on paid developers, and Shipyard had been one of them. The wind-down strips the IPFS ecosystem of a team that was actively writing code and maintaining parts of the infrastructure. No details were given on which specific initiatives were affected, but the whole IPFS workload is being shelved.

Translation:

O IPFS é um projeto de código aberto, mas código aberto não significa que seja gratuito para construir. As contribuições dependem de desenvolvedores pagos, e a Shipyard era uma delas. O encerramento retira do ecossistema IPFS uma equipe que estava ativamente escrevendo código e mantendo partes da infraestrutura. Nenhum detalhe foi dado sobre quais iniciativas específicas foram afetadas, mas toda a carga de trabalho do IPFS está sendo arquivada.

Next:

What the wind-down means for the protocol

->

O que o encerramento significa para o protocolo

Paragraph:

The protocol itself is still alive. It's used by a range of decentralized apps and has a community of independent contributors. But losing a funded development partner is a concrete setback. IPFS's roadmap may slow down, and some planned features could take longer to land or never arrive. The exact impact won't be clear until the wind-down is complete.

Translation:

O protocolo em si ainda está vivo. Ele é usado por uma variedade de aplicativos descentralizados e tem uma comunidade de contribuidores independentes. Mas perder um parceiro de desenvolvimento financiado é um revés concreto. O roteiro do IPFS pode desacelerar, e alguns recursos planejados podem demorar mais para chegar ou nunca chegar. O impacto exato não ficará claro até que o encerramento seja concluído.

Last paragraph:

No timeline was announced, and there's no word on whether Shipyard might return to IPFS if new funding appears. Protocol Labs has also stayed silent on the matter. For now, the IPFS community is left to sort out how to fill the gap.

Translation:

Nenhum cronograma foi anunciado, e não há notícias sobre se a Shipyard poderá retornar ao IPFS se novos financiamentos aparecerem. A Protocol Labs também permaneceu em silêncio sobre o assunto. Por enquanto, a comunidade IPFS fica para resolver como preencher a lacuna.

Now meta description: Original: "Shipyard is winding down its IPFS work after Protocol Labs stops funding. The move leaves the decentralized web protocol with fewer developers." Translation: "A Shipyard está encerrando seu trabalho no IPFS após a Protocol Labs interromper o financiamento. A medida deixa o protocolo web descentralizado com menos desenvolvedores." We need to output JSON with title, content (the whole article HTML), and meta.description. Make sure to preserve HTML structure exactly, with
and

,

tags. We'll wrap the translated content in
as in original. Let's assemble the content: We'll have the article tag with the translated paragraphs and headings. We'll put the title as a string. Now, ensure proper Portuguese: Use "a Shipyard" (feminine? Actually "Shipyard" is a company name, we can use "a Shipyard" as it's a company, but in Portuguese we often use "a empresa Shipyard" or just "Shipyard" without article. But in the original they say "Shipyard is winding down" - we can say "A Shipyard está encerrando" or "Shipyard está encerrando". I'll use "A Shipyard" for clarity, but it's optional. I'll use "A Shipyard" in the first mention, then "a Shipyard" later. Actually in the original they use "Shipyard" without article. In Portuguese, we often use article for companies: "A Apple", "A Microsoft". So I'll use "A Shipyard" consistently. But in the title, we have "Shipyard" as subject, we can say "Shipyard encerra" but better "A Shipyard encerra". I'll use "A Shipyard" in title? The title is "Shipyard Winds Down..." - we can translate as "A Shipyard encerra..." but the original doesn't have "The". I'll keep it as "Shipyard encerra" but it's fine. Actually to be natural, I'll use "A Shipyard" in the body, but in the title I'll keep "Shipyard" as it's a proper noun. I'll decide: In the title, I'll write "Shipyard encerra trabalho no IPFS após Protocol Labs interromper financiamento" - no article. In the body, I'll use "A Shipyard" for the first mention, then "a Shipyard" later. But the original uses "Shipyard" without article. I'll follow the original style: use "Shipyard" without article, but in Portuguese it's common to use article. I'll use "A Shipyard" in the first sentence to be clear, but then later "a Shipyard". Actually, let's be consistent: I'll use "A

Artigos Relacionados

The9 registra lucro líquido de US$ 32,4 milhões no 2º trimestre com ganhos de tokens 9BIT, não mineraçãoThe9 registra lucro líquido de US$ 32,4 milhões no 2º trimestre com ganhos de tokens 9BIT, não mineraçãoCriptoless than a minute agoDexsport Tops Crypto Sportsbooks for Boxing and MMA CoverageDexsport Tops Crypto Sportsbooks for Boxing and MMA CoverageCripto11 minutes agoLayerZero Unveils ATLAS Exchange, Bringing Citadel Securities and DTCC On BoardLayerZero Unveils ATLAS Exchange, Bringing Citadel Securities and DTCC On BoardCripto20 minutes agois not given, but we can infer from the content. The original title might beis not given, but we can infer from the content. The original title might beCripto29 minutes ago