#peer-to-peer #libp2p #networking


Multistream-select negotiation protocol for libp2p

6 releases

0.10.3 Apr 15, 2021
0.10.2 Mar 5, 2021
0.9.2 Feb 5, 2021
0.9.1 Jan 7, 2021
0.8.2 Dec 31, 2020

#1069 in Network programming

Download history 74/week @ 2022-06-01 35/week @ 2022-06-08 15/week @ 2022-06-15 41/week @ 2022-06-22 25/week @ 2022-06-29 35/week @ 2022-07-06 36/week @ 2022-07-13 51/week @ 2022-07-20 38/week @ 2022-07-27 53/week @ 2022-08-03 92/week @ 2022-08-10 40/week @ 2022-08-17 38/week @ 2022-08-24 51/week @ 2022-08-31 99/week @ 2022-09-07 53/week @ 2022-09-14

241 downloads per month
Used in 22 crates (via fluence-fork-libp2p-core)

MIT license

1.5K SLoC

Central repository for work on libp2p

dependency status Crates.io docs.rs

This repository is the central place for Rust development of the libp2p spec.

Getting started

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.

  • 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.


  • Be respectful.
  • We're here to help: abuse@ipfs.io
  • 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.


(In alphabetical order.)

Notable users

(open a pull request if you want your project to be added here)


~38K SLoC