libp2p /rust-libp2p
The Rust Implementation of the libp2p networking stack.
★ 5,645⑂ 1,280👁 98⑃ 4,786● 1,419▤ 39
+0
日增长
5,645
stars
1,280
forks
98
watchers
4,786
prs
1,419
issues
39
releases
README
Central repository for work on libp2p
This repository is the central place for Rust development of the libp2p spec.
Getting started
- Main documentation can be found on https://docs.rs/libp2p.
- The examples folder contains small binaries showcasing the
many protocols in this repository.
- For security related issues please file a private security vulnerability
report . Please do not file a
public issue on GitHub.
- To report bugs, suggest improvements or request new features please open a
GitHub issue on this repository.
- For rust-libp2p specific questions please use the GitHub _Discussions_
forum https://github.com/libp2p/rust-libp2p/discussions.
- For discussions and questions related to multiple libp2p implementations
please use the libp2p _Discourse_ forum https://discuss.libp2p.io.
- For synchronous discussions join the open rust-libp2p maintainer
calls
or the biweekly libp2p community calls.
Repository Structure
The main components of this repository are structured as follows:
core/: The implementation of libp2p-core with its Transport and
StreamMuxer API on which almost all other crates depend.
transports/: Implementations of transport protocols (e.g. TCP) and protocol upgrades
(e.g. for authenticated encryption, compression, ...) based on the libp2p-core Transport
API.
muxers/: Implementations of the StreamMuxer interface of libp2p-core,
e.g. (sub)stream multiplexing protocols on top of (typically TCP) connections.
Multiplexing protocols are (mandatory) Transport upgrades.
swarm/: The implementation of libp2p-swarm building on libp2p-core
with the central interfaces NetworkBehaviour and ConnectionHandler used
to implement application protocols (see protocols/).
protocols/: Implementations of application protocols based on the
libp2p-swarm APIs.
misc/: Utility libraries.
libp2p/examples/: Worked examples of built-in application protocols (see protocols/)
with common Transport configurations.
Community Guidelines
The libp2p project operates under the IPFS Code of
Conduct.
tl;dr
- Be respectful.
- We're here to help: [email protected]
- Abusive behavior is never tolerated.
- Violations of this code may result in swift and permanent expulsion from the
IPFS [and libp2p] community.
- "Too long, didn't read" is not a valid excuse for not knowing what is in
this document.
Maintainers
(In alphabetical order.)
- Elena Frank (@elenaf9)
- João Oliveira (@jxs)
Notable users
(open a pull request if you want your project to be added here)
- COMIT - Bitcoin–Monero Cross-chain Atomic Swap.
- Forest - An implementation of Filecoin written in Rust.
- fuel-core - A Rust implementation of the Fuel protocol.
- HotShot - Decentralized sequencer in Rust developed by Espresso Systems.
- ipfs-embed - A small embeddable ipfs implementation used and maintained by Actyx.
- Homestar - An InterPlanetary Virtual Machine (IPVM) implementation used andTop issues
#2398protocols/gossipsub: Support peer exchange28 comments · 2021-12-21#4817Update libp2p_kad::store::RecordStore trait to be amenable to a persistent implementation19 comments · 2023-11-07#3659Switch from `webrtc-rs` to `str0m`19 comments · 2023-03-22#4007dialing client raised `Connection closed with error NoAddresses`, relay server log is `no protocol could be agreed upon for inbound stream`17 comments · 2023-05-30#4389webrtc-websys: implement `webrtc` protocol for browser-to-browser communication16 comments · 2023-08-24#2993transport/webtransport: Add WebTransport protocol16 comments · 2022-10-06#5313kad: consume `FromSwarm::NewExternalAddrOfPeer`15 comments · 2024-04-15#5097Persistent peer identity during restart make it unable to publish message with gossipsub15 comments · 2024-01-16
Discussions
#6700Why `GetProvidersOk` returns `PeerId` only instead of `PeerInfo`?1 comments · 2026-10-19#6699Ignore response with empty `provider_peers` when handling `GetProvidersRes`?0 comments · 2026-10-19#6696function `discovered` in `./protocols/kad/src/behaviour.rs` will always replace existing `multiaddr` with new ones instead of appending, is this a bug?1 comments · 2026-10-18#6632Gossipsub default values: a few questions from the Forest team2 comments · 2026-09-22#6584ProbeLab's Measurement Study of libp2p's DCUtR protocol0 comments · 2026-08-05#6523connection duration1 comments · 2026-07-14#6522ProbeLab's Performance Audit of libp2p’s AutoNAT0 comments · 2026-07-13#6508Introducing KID: A Permanent Identity Layer for kinetic0 comments · 2026-07-02
Latest release
libp2p-v0.57.1 v0.57.1 2026-10-15Publish libp2p-peer-store v0.1.0 and include it in libp2p v0.57.1 as a feature