Deprecation Schedule and Removal Tracker

Monitor the removal of legacy API endpoints, deprecated plugin interfaces, and the ongoing extraction of core logic into the boxo library. Operators must track the sunset of the go-ipfs configuration profile and the mandatory migration to boxo-based architectures to avoid breaking changes in plugin loading and configuration injection. Review the specific Kubo release notes for the exact version where deprecated commands like ipfs object and ipfs file are removed.

Track the phased removal of insecure and obsolete transports across all implementations. The SECIO security transport is already removed. Monitor the deprecation timeline for QUIC draft versions (e.g., draft-29) in favor of QUICv1, and the planned removal of the legacy TCP transport in environments where WebTransport and WebRTC are viable. Operators should audit their node's advertised addresses to ensure they do not rely on deprecated multiaddr components.

The legacy js-ipfs package is fully deprecated. The Helia migration watchlist tracks the final end-of-life milestones for any remaining compatibility shims. Teams must migrate to the modular Helia architecture, replacing direct js-ipfs API calls with the new helia and @helia/* packages. A critical action is verifying that custom libp2p configurations in a browser context are compatible with Helia's default WebRTC and WebTransport transports.

The legacy Kad-DHT is being phased out in favor of the Amino DHT and IPNI-based content routing. This watchlist tracks the removal of the old DHT client and server modes in Kubo and go-libp2p. Operators must ensure their nodes are configured to participate in the Amino DHT to maintain content discoverability. A key signal is the default change of Routing.Type from dht to auto or amino in a future Kubo release.

Public and private gateway operators must track the deprecation of path-based resolution in favor of subdomain isolation for security. Monitor the removal of the legacy /api/v0 RPC endpoints on public gateways and the enforcement of stricter CORS and rate-limiting defaults. The watchlist includes the planned removal of the X-Ipfs-Gateway-Prefix header and the transition to the new gateway specification's pathing conventions.

A deprecation on this watchlist can silently break content retrieval, peer connectivity, or API integrations. Chainscore Labs performs a targeted impact assessment against your specific tech stack—auditing your Kubo configuration, Helia integration code, or custom libp2p host setup. We deliver a prioritized remediation plan with exact version pinning, configuration migration scripts, and a testing suite to validate compatibility before you upgrade production infrastructure.

Kubo is the primary operational reference for many production IPFS nodes, gateways, pinning backends, and private clusters. Review each release for breaking configuration changes, removed commands, repository migrations, transport defaults, gateway behavior, and dependency updates inherited from go-libp2p and Boxo. Operators should compare the release notes against deployed versions, custom configs, Docker images, Kubernetes manifests, and API clients before upgrading. Pay particular attention to changes affecting the HTTP API, gateway resolution, datastore behavior, garbage collection, DHT routing, and resource limits.

Helia is the active modular JavaScript IPFS implementation and is the practical migration target for many projects that previously embedded js-ipfs. Use Helia releases to identify API changes, package splits, transport support, blockstore and datastore expectations, and browser-versus-Node.js compatibility requirements. Wallets, dapps, NFT tools, and browser-based storage clients should test imports, bundling, CORS behavior, WebRTC/WebTransport availability, and CID handling before replacing legacy JS IPFS dependencies. Treat any deprecation in the Helia package graph as an integration-level change, not just a dependency bump.

The libp2p specs repository is the canonical place to verify transport, security, stream-multiplexing, peer routing, relay, identify, and connection-management semantics. Before removing support for an older protocol or enabling a newer one by default, teams should confirm the relevant protocol IDs, negotiation behavior, backward-compatibility assumptions, and implementation status. This is especially important for mixed fleets where Kubo, go-libp2p services, rust-libp2p nodes, browser clients, and mobile clients must still connect across NATs, relays, and public DHT infrastructure.

go-libp2p changes can affect Kubo, custom Go IPFS services, indexers, crawlers, gateways, and private networking stacks even when the application code has not changed. Monitor release notes for deprecated interfaces, resource manager behavior, transport changes, security protocol defaults, relay behavior, connection gating, and peerstore or address-management changes. Teams running Go-based infrastructure should pin versions intentionally, run connectivity tests across representative peers, and check whether application-level assumptions still hold after dependency upgrades.

Deprecation impact is not uniform across implementations. A protocol may be specified, experimental, enabled by default, or removed at different times in rust-libp2p and js-libp2p. Teams building browsers, wallets, desktop apps, Substrate-adjacent systems, custom content routers, or embedded peer-to-peer clients should review implementation-specific release notes before assuming compatibility with Kubo or go-libp2p nodes. Maintain a matrix of supported transports, security protocols, multiplexers, relay behavior, and target runtimes, then test cross-implementation dialing and stream negotiation before production rollout.

The IPFS specifications site is the reference layer for content addressing, CIDs, UnixFS, CAR files, gateways, HTTP APIs, and related interoperability rules. Use it to distinguish protocol-level compatibility from implementation-specific release behavior. When a deprecation affects CID codecs, gateway semantics, path resolution, DAG formats, or API expectations, builders should validate stored content, indexing pipelines, pinning workflows, and client libraries against the relevant spec before changing production behavior. Chainscore can turn these sources into a stack-specific deprecation impact assessment and migration checklist.