kubo/docs/changelogs/v0.30.md

Kubo changelog v0.30

• v0.30.0

v0.30.0

• Overview
• 🔦 Highlights
  • WebRTC-Direct Transport enabled by default
  • Automated ipfs version check
  • Version Suffix Configuration
• 📝 Changelog
• 👨‍👩‍👧‍👦 Contributors

Overview

🔦 Highlights

WebRTC-Direct Transport enabled by default

Kubo now ships with /udp/4001/webrtc-direct listener enabled by default.

WebRTC Direct complements existing /wss (Secure WebSockets) and /webtransport transports. Unlike /wss, which requires a domain name and a CA-issued TLS certificate, WebRTC Direct works with IPs and can be enabled by default on all Kubo nodes.

Learn more: Swarm.Transports.Network.WebRTCDirect

Note

Kubo 0.30 includes a migration for existing users that adds /webrtc-direct listener on the same UDP port as /udp/{port}/quic-v1. This supports the WebRTC-Direct rollout by reusing preexisting UDP firewall settings and port mappings created for QUIC.

Automated ipfs version check

Kubo now performs privacy-preserving version checks using the libp2p identify protocol on peers detected by the Amino DHT client. If more than 5% of Kubo peers seen by your node are running a newer version, you will receive a log message notification.

• For manual checks, refer to ipfs version check --help for details.
• To disable automated checks, set Version.SwarmCheckEnabled to false.

Version Suffix Configuration

Defining the optional agent version suffix is now simpler. The Version.AgentSuffix value from the Kubo config takes precedence over any value provided via ipfs daemon --agent-version-suffix (which is still supported).

Note

Setting a custom version suffix helps with ecosystem analysis, such as Amino DHT reports published at https://stats.ipfs.network

📝 Changelog

👨‍👩‍👧‍👦 Contributors