libp2p/py-libp2p is a Python project with 628 stars. The Python implementation of the libp2p networking stack π [under development]
Snapshot summary built from the project's own GitHub metadata β there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then β see the READ ME tab for the original README in full.
The Python implementation of the libp2p networking stack.
py-libp2p has moved beyond its experimental roots and is steadily progressing toward production readiness. The core features are stable, and weβre focused on refining performance, expanding protocol support, and ensuring smooth interop with other libp2p implementations. We welcome contributions and real-world usage feedback to help us reach full production maturity.
Read more in the documentation on ReadTheDocs. View the release notes.
Maintainers
Currently maintained by @pacrob, @seetadev, @sumanjeet, @luca and @dhuseby. Please reach out to us for collaboration or active feedback. If you have questions, feel free to open a new discussion. We are also available on the libp2p Discord β join us at #py-libp2p sub-channel.
Feature Breakdown
py-libp2p aims for conformity with the standard libp2p modules. Below is a breakdown of the modules we have developed, are developing, and may develop in the future.
WebRTC-Direct (browser/server) uses the spec STUN path by default: inbound
dials hit a shared UDP port and the listener infers the offer from the first
STUN packet; outbound dials synthesise an ICE-Lite answer from the multiaddr
with no default public STUN servers. This is the only signalling path that
interoperates with go-libp2p / js-libp2p / browsers. An experimental HTTP
POST /sdp harness (WebRTCTransportConfig(enable_sdp_http_harness=True)) is
for pyβpy debugging only and is not interoperable β leave it off in
production.
Choosing a dial version. The listener always accepts both v1 and v2; the
dialer picks with WebRTCTransportConfig(webrtc_direct_dial_version=1|2):
v1 (default today) β the migration path (SDP ufrag/pwd munging). Kept as
the default while go/js dialers still start on v1 for wider-network
compatibility; the listener already accepts both.
v2 (recommended) β the specs#715
flow (merged), no SDP munging. Prefer it for new deployments; browser
dialling needs v2 once NoSdpMangleUfrag support is widespread. Opt in with
webrtc_direct_dial_version=2; the default flips to v2 when the network is
ready, not merely because the spec has landed.
NAT Traversal
NAT Traversal
Status
Source
libp2p-circuit-relay-v2
β
source
libp2p-autonat
β
source
libp2p-hole-punching
β
source
Secure Communication
Secure Communication
Status
Source
libp2p-noise
β
source
libp2p-tls
β
Discovery
Discovery
Status
Source
bootstrap
β
source
random-walk
β
source
mdns-discovery
β
source
rendezvous
β
source
Peer Routing
Peer Routing
Status
Source
libp2p-kad-dht
β
source
Publish/Subscribe
Publish/Subscribe
Status
Source
libp2p-floodsub
β
source
libp2p-gossipsub
β
source
Stream Muxers
Stream Muxers
Status
Source
libp2p-yamux
β
source
libp2p-mplex
β
source
Storage
Storage
Status
libp2p-record
β
General Purpose Utilities & Datatypes
Utility/Datatype
Status
Source
libp2p-ping
β
source
libp2p-peer
β
source
libp2p-identify
β
source
Identity Persistence
For a stable Peer ID across restarts, use opt-in identity helpers (default
new_host() behavior is unchanged and still generates a random Ed25519 key):
Key-pair provider:new_host(key_pair_provider=...) accepts
Callable[[], KeyPair] as described in issue #312.
Filesystem keystore:FileSystemKeyStore stores named keys under a directory;
pass new_host(keystore=..., identity_name="default") to load or auto-persist.
Prefer these APIs over the legacy PEM helpers save_keypair / load_keypair
(Ed25519-only, fixed path).
Example (keystore)::
from pathlib import Path
from libp2p import new_host
from libp2p.crypto.keystore import FileSystemKeyStore
store = FileSystemKeyStore(Path.home() / ".config" / "py-libp2p" / "keystore")
host = new_host(keystore=store, identity_name="default")
# Subsequent runs with the same store/name reuse the same Peer ID.
Explanation of Basic Two Node Communication
Core Concepts
(non-normative, useful for team notes, not a reference)
Several components of the libp2p stack take part when establishing a connection between two nodes:
Host: a node in the libp2p network.
Connection: the layer 3 connection between two nodes in a libp2p network.
Transport: the component that creates a Connection, e.g. TCP, UDP, QUIC, etc.
Streams: an abstraction on top of a Connection representing parallel conversations about different matters, each of which is identified by a protocol ID. Multiple streams are layered on top of a Connection via the Multiplexer.
Multiplexer: a component that is responsible for wrapping messages sent on a stream with an envelope that identifies the stream they pertain to, normally via an ID. The multiplexer on the other unwraps the message and routes it internally based on the stream identification.
Secure channel: optionally establishes a secure, encrypted, and authenticated channel over the Connection.
Upgrader: a component that takes a raw layer 3 connection returned by the Transport, and performs the security and multiplexing negotiation to set up a secure, multiplexed channel on top of which Streams can be opened.
Communication between two hosts X and Y
(non-normative, useful for team notes, not a reference)
Initiate the connection: A host is simply a node in the libp2p network that is able to communicate with other nodes in the network. In order for X and Y to communicate with one another, one of the hosts must initiate the connection. Let's say that X is going to initiate the connection. X will first open a connection to Y. This connection is where all of the actual communication will take place.
Communication over one connection with multiple protocols: X and Y can communicate over the same connection using different protocols and the multiplexer will appropriately route messages for a given protocol to a particular handler function for that protocol, which allows for each host to handle different protocols with separate functions. Furthermore, we can use multiple streams for a given protocol that allow for the same protocol and same underlying connection to be used for communication about separate topics between nodes X and Y.
Why use multiple streams?: The purpose of using the same connection for multiple streams to communicate over is to avoid the overhead of having multiple connections between X and Y. In order for X and Y to differentiate between messages on different streams and different protocols, a multiplexer is used to encode the messages when a message will be sent and decode a message when a message is received. The multiplexer encodes the message by adding a header to the beginning of any message to be sent that contains the stream id (along with some other info). Then, the message is sent across the raw connection and the receiving host will use its multiplexer to decode the message, i.e. determine which stream id the message should be routed to.
TopGit's last sync did not record any GitHub topics for libp2p/py-libp2p. GitHub topics appear in the right sidebar of a repository page; that's the authoritative place to check.
How active is development on libp2p/py-libp2p?
The most recent commit recorded on libp2p/py-libp2p was today, based on the GitHub push timestamp. The repository has 260 forks β one of the better signals of community interest.
How many stars does libp2p/py-libp2p have?
libp2p/py-libp2p has 628 GitHub stars β refresh the page for the live number, or check github.com/libp2p/py-libp2p. TopGit mirrors GitHub's count but does not claim minute-by-minute accuracy.
Is libp2p/py-libp2p open source?
TopGit's metadata for libp2p/py-libp2p does not record a license. Most public repositories on GitHub ARE open source, but the exact terms vary β verify by opening the LICENSE file directly.
Where can I see libp2p/py-libp2p in action?
The project maintains a homepage at https://libp2p.io. The README tab on this page also usually contains screenshots and a quickstart.
Where do I read more about libp2p/py-libp2p?
This TopGit page is a snapshot β the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/libp2p/py-libp2p is the definitive source.
Read full README in the tab above.
Curious whether py-libp2p is right for you?
Let ChatGPT, Claude, or Perplexity look into it β click below and see what AI actually says about py-libp2p.