Operations and Releases
Documents significant releases, deprecations, and configuration changes for core implementations such as Kubo (go-ipfs), Helia (JS IPFS), go-libp2p, rust-libp2p, and js-libp2p. Node operators, pinning services, and gateway providers rely on this group to understand resource usage changes, default security posture shifts, migration requirements, and performance regressions that directly affect production infrastructure.
Kubo (go-ipfs) Release History and Breaking Changes
A chronological impact index of significant Kubo releases. Each entry highlights breaking changes, default configuration shifts, new features, and migration steps. Node operators and infrastructure providers use this to plan upgrades, assess operational risk, and understand the blast radius of a new version. Chainscore can provide an upgrade readiness review for teams managing fleets of Kubo nodes.
Helia (JS IPFS) Release and Migration Guide
Tracks major Helia releases and the evolving modular architecture. Covers breaking API changes, new default transports and codecs, and migration paths from the deprecated `js-ipfs` package. Essential for browser-based dapp developers and Node.js service operators. Chainscore can audit integration code for compatibility with the latest Helia APIs.
go-libp2p Release Notes and Breaking Changes
A dedicated page for the Go implementation of libp2p. Documents changes to core interfaces, transport deprecations (e.g., SECIO), multiplexer defaults, and resource manager tuning. Go node operators and Kubo developers depend on this to manage their dependency graph. Chainscore can review custom libp2p host configurations for post-upgrade regressions.
rust-libp2p Release and Stability Report
Tracks the release cadence and stability guarantees of the Rust implementation. Covers breaking API changes, new protocol implementations, and async runtime compatibility. Critical for teams building Rust-based IPFS nodes or Substrate/Polkadot integrations. Chainscore can assess the impact of a new rust-libp2p release on a project's networking layer.
js-libp2p Release and Browser Compatibility
Documents releases of the JavaScript implementation, with a focus on browser and Node.js compatibility. Highlights changes to WebRTC and WebTransport transports, noise encryption defaults, and connection manager behavior. A key resource for dapp and wallet developers embedding peer-to-peer networking in web contexts. Chainscore can review a dapp's transport configuration for connectivity risks.
Default Configuration Changes and Tuning Guide
A cross-implementation page that tracks significant shifts in default settings, such as the libp2p resource manager limits, connection manager high/low watermarks, and automatic GC thresholds. Operators use this to understand why node behavior changed after an upgrade and how to tune it for their specific infrastructure. Chainscore can provide a parameter audit and tuning recommendation for production deployments.
Deprecation Schedule and Removal Tracker
A forward-looking calendar of feature and protocol deprecations across all core implementations. Tracks the planned removal of old transports (e.g., QUIC draft versions), insecure protocols, and legacy APIs. This is a planning tool for operators to ensure their infrastructure remains compatible and secure. Chainscore can perform a deprecation impact assessment for a client's tech stack.
Resource Usage and Performance Regression Reports
Analyzes known performance regressions in major releases, focusing on CPU, memory, and bandwidth. Documents the impact of changes like new DHT routing algorithms or Bitswap optimizations. Node operators and pinning services use this to pre-emptively scale resources or delay an upgrade. Chainscore can conduct a performance regression review before a client rolls out a new version.
Gateway Configuration and Policy Changes
Tracks operational changes for public and private IPFS gateways. Covers new path resolution behaviors, CORS header defaults, denylist management, and rate-limiting configurations. Gateway providers rely on this page to maintain a secure and performant public service. Chainscore can review a gateway's configuration and policy enforcement for security gaps.
Pinning Service API and Operational Changes
Documents changes to the IPFS Pinning Service API specification and its implementation in major clients. Covers new pinning policies, background maintenance tasks, and migration requirements for pinning service backends. Critical for platforms like Pinata, web3.storage, and NFT.storage. Chainscore can help a pinning service plan and execute a backend migration with zero data loss.
Content Routing and DHT Operational Shifts
Tracks operational changes to content routing systems, including the Amino DHT, IPNI, and the transition away from the legacy Kad-DHT. Covers changes to peer record validity, provider record lifetimes, and routing table refresh logic. Operators use this to diagnose content availability issues. Chainscore can investigate content routing failures and recommend configuration fixes.
Data Transfer and Bitswap Performance Tuning
Documents operational aspects of the Bitswap protocol and its implementations. Covers new session management strategies, block-presence exchange logic, and configuration knobs for optimizing transfer speed versus bandwidth usage. Essential for operators running data-heavy IPFS nodes. Chainscore can analyze a node's Bitswap performance and provide a tuning guide for specific workloads.
Accelerated Client Migration Paths
A practical guide for operators migrating from older or deprecated clients (e.g., `js-ipfs` to Helia, or `go-ipfs` to a future Rust-based node). Provides side-by-side configuration mappings, data repository migration steps, and API compatibility notes to minimize downtime. Chainscore can manage and execute a full-stack migration for a client's IPFS infrastructure.
Production Readiness and Deployment Patterns
A meta-page that links to reference architectures, Docker/Kubernetes deployment guides, and monitoring best practices. Covers health checks, log analysis, and alerting thresholds for running IPFS and libp2p nodes in production, updated as new releases change the operational landscape. Chainscore can design and implement a production-grade monitoring and alerting suite for an IPFS deployment.
Kubo to Boxo Migration Impact
Tracks the operational impact of the ongoing extraction of core IPFS logic from Kubo into the reusable `boxo` library. Documents how this refactoring changes plugin loading, configuration injection, and upgrade paths for operators who have customized their Kubo nodes. Chainscore can review custom Kubo plugins and provide a migration plan to a `boxo`-based architecture.
libp2p Hole Punching and NAT Traversal Reliability
An operations-focused page on the real-world reliability of libp2p's hole-punching (DCUtR) and relay (circuit-relay-v2) systems. Tracks changes in relay defaults, address discovery, and auto-relay behavior that directly impact connectivity for nodes behind restrictive firewalls and NATs. Chainscore can diagnose connectivity issues and optimize a node's NAT traversal strategy.
Security Posture and CVE Response History
A chronological record of security advisories and CVEs affecting core implementations. For each, it details the vulnerable versions, the operational workaround, and the release containing the fix. Operators use this to audit their infrastructure and prioritize patching. Chainscore can perform a version audit of a client's infrastructure to identify unpatched critical vulnerabilities.