IPFS Maintainers Winding Down

Original Article ↗ Hacker News Discussion ↗

IPFS’s main maintenance team at Shipyard is being wound down after Protocol Labs declined to renew funding, raising concerns about the long‑term support of core implementations like Kubo, Boxo, Helia, and public gateways such as ipfs.io and dweb.link. Commenters debate whether IPFS ever found a compelling use case beyond crypto and NFTs, citing chronic performance, UX, and governance issues, while noting it still underpins some censorship‑resistant archiving, generative art, and piracy mirrors. Alternatives such as Iroh, BitTorrent, Arweave, and other content‑addressed or peer‑to‑peer systems are highlighted as either more practical successors or evidence that IPFS was an elegant idea that never escaped “cool tech in search of a problem” territory.

What actually happened

  • Shipyard, a major IPFS maintainer and operator of key public infra, is shutting down after Protocol Labs ended funding.
  • Several commenters stress that IPFS as a protocol/network is not formally “shutting down,” but losing a central funded maintainer team is widely seen as serious.

Funding, governance, and infrastructure concerns

  • Protocol Labs is criticized for pivoting to other buzzword-heavy areas (crypto, then AI) and defunding core IPFS work.
  • People ask who will own security triage, commits, and releases for Kubo, Boxo, Helia, gateways (ipfs.io, dweb.link, delegated-ipfs.dev), Service Worker Gateway, and Badbits after Sept 30; answers are unclear.
  • Individual maintainer grants are viewed as weaker than a clearly responsible team with release processes.

Technical experiences and limitations

  • Multiple reports of IPFS nodes being slow (multi-minute lookups), chatty, and operationally painful (UDP storms, poor caching, double writes, cache eviction spikes).
  • DHT-based global content discovery is called “very hard” and may have been a design mistake; performance of the public network is often described as bad.
  • IPNS and browser-based IPFS (js-ipfs, Brave support) are viewed as unreliable or removed; many real-world apps ended up hiding behind HTTP gateways, which some call “decentralization theater.”

Perceived use cases vs reality

  • Hoped-for use cases: censorship-resistant archiving, reproducible web apps, content-addressed web, P2P software distribution, “better BitTorrent,” NFT asset hosting, piracy-resilient mirrors (libgen, sci-hub).
  • In practice, common mentions are NFTs, libgen, sci-hub mirrors, some generative art, and a few production systems (e.g., large-scale gateway traffic, artifact distribution).
  • Several conclude IPFS was “cool tech looking for a problem” and that HTTP + CDNs + BitTorrent are “good enough” for most needs.

Alternatives and successor technologies

  • Iroh (multipath QUIC + blobs/gossip) is highlighted as a lower-level, more focused primitive; can recreate IPFS-like functionality but lacks global discovery so far.
  • DASL, AT Protocol (Bluesky), Radicle, Arweave, Hyphanet/Freenet, Tor-style resolvers, and named-data networking are mentioned as related or successor directions.
  • Some hope AI-assisted maintenance could revive abandoned OSS like IPFS components.

Legal, ethical, and adoption issues

  • Concerns about hosting illegal content (especially for public gateways) are cited as a deterrent; IPFS itself does not force hosting unwanted data, but gateways face abuse and need deny-lists.
  • Skepticism that “censorship resistance” actually works at scale, given how easily clients/gateways could be blocked.

Crypto, NFTs, and trust in new tech

  • Strong backlash to crypto/Filecoin entanglement and NFT grifts; many see IPFS’s reputation damaged by association.
  • Some note that most NFTs are just pointers (often IPFS or S3 URLs), not on-chain assets, which disillusioned many.
  • Several connect current AI skepticism to burn-out from the crypto/NFT hype cycle.

Community sentiment and future

  • Mix of nostalgia, disappointment, and mild optimism that ideas like content-addressing will reappear in better-designed systems.
  • A few people are looking for IPFS replacements (e.g., for music distribution) or offering to work on related tech; others think investing further in IPFS itself is likely a dead end.