43 releases (breaking)
|0.31.0||Jul 12, 2021|
|0.29.0||Mar 17, 2021|
|0.27.0||Dec 18, 2020|
|0.26.0||Nov 25, 2020|
|0.6.0||Mar 29, 2019|
#916 in Network programming
42,679 downloads per month
Used in 39 crates (via libp2p)
This repository is the central place for Rust development of the libp2p spec.
Main documentation can be found on https://docs.rs/libp2p.
The examples folder contains small binaries showcasing the many protocols in this repository.
To report bugs, suggest improvements or request new features please open 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.
The main components of this repository are structured as follows:
core/: The implementation of
StreamMuxerAPI 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
muxers/: Implementations of the
libp2p-core, e.g. (sub)stream multiplexing protocols on top of (typically TCP) connections. Multiplexing protocols are (mandatory)
swarm/: The implementation of
libp2p-corewith the central interfaces
ProtocolsHandlerused to implement application protocols (see
protocols/: Implementations of application protocols based on the
misc/: Utility libraries.
examples/: Worked examples of built-in application protocols (see
protocols/) with common
The libp2p project operates under the IPFS Code of Conduct.
- Be respectful.
- We're here to help: firstname.lastname@example.org
- 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.
(open a pull request if you want your project to be added here)