Support libp2pDonate Now
v0.55 shipped · QUIC, WebRTC, WebTransport

The modular networking stack for decentralized systems

Peer-to-peer transports, NAT traversal, peer routing, and pub/sub — composed into a production-proven networking layer used by IPFS, Ethereum, and beyond.

// pulse

Project at a glance

auto-updated nightly
Total Repositories
0+
All repositories ecosystem-wide since libp2p inception
Monthly Commits
0+
Merged across all repos · last 30 days
Implementations
0
Go, Rust, JS, Nim, Java, …
AI/ML projects leveraging libp2p
0+
Across agentic systems, federated learning, and inference networks
// why libp2p

Built for the realities of the open internet

Modular stack

Swap transports, muxers, security, and routing — pick the primitives you need.

Many transports

TCP, QUIC, WebRTC, WebTransport, WebSockets — browser to backbone.

NAT traversal

Hole-punching, AutoNAT, and relays connect peers across hostile networks.

Production-proven

Powers IPFS, Ethereum, Polkadot and more at internet scale.

// roadmap

What improvements are coming to libp2p

The next wave of upgrades focuses on stronger security, faster transports, network resilience, and pub/sub at AI-agent scale.

Stronger security

Upgrades to Noise and TLS handshakes harden every connection and prepare libp2p for the post-quantum era.

Better Web Transport

Web Transport improvements unlock agentic features and deliver faster, more reliable browser-native networking.

Resilience as a protocol

New primitives turn resilience into a first-class protocol so networks self-heal under churn, attacks, and hostile NATs.

GossipSub 1.4

Next-gen pub/sub scales to large agent conversations and interoperates with AI platforms like Hugging Face.

Next Hop

Shipping soon
  • Browser-to-browser WebRTC by default
  • AutoNAT v2 and smarter hole punching
  • Universal connectivity across runtimes
  • Improved DCUtR success rates in the wild

Long Haul

On the horizon
  • Post-quantum handshakes end-to-end
  • First-class libp2p mesh for AI agents
  • Bandwidth & reputation-aware peer routing
  • Native mobile transports with background peering
// heat maps

Implementation health at a glance

Compare every libp2p implementation across spec completeness, protocol support, maintenance activity, test coverage, and roadmap progress. Greener cells mean healthier; warmer cells flag gaps where contributors are most welcome.

ImplementationSpec completenessProtocol supportMaintenance activityTest coverageRoadmap progress
go-libp2p
Go
95%
92%
88%
84%
70%
rust-libp2p
Rust
90%
88%
92%
86%
75%
js-libp2p
TypeScript
82%
80%
78%
72%
65%
nim-libp2p
Nim
70%
68%
65%
70%
50%
zig-libp2p
Zig
35%
30%
60%
28%
25%
py-libp2p
Python
45%
42%
38%
40%
30%
jvm-libp2p
Kotlin/Java
55%
52%
50%
58%
35%
Legend0–2425–3940–5455–6970–8485–100