#p2p #peer-to-peer #networking


A simple, low-level, and customizable implementation of a TCP P2P node

65 releases (breaking)

0.48.0 Jul 3, 2023
0.46.0 Apr 24, 2023
0.45.0 Jan 13, 2023
0.44.0 Dec 23, 2022
0.8.0 Dec 31, 2020

#1348 in Network programming

Download history 185/week @ 2023-08-02 123/week @ 2023-08-09 288/week @ 2023-08-16 139/week @ 2023-08-23 266/week @ 2023-08-30 260/week @ 2023-09-06 315/week @ 2023-09-13 479/week @ 2023-09-20 292/week @ 2023-09-27 367/week @ 2023-10-04 293/week @ 2023-10-11 518/week @ 2023-10-18 389/week @ 2023-10-25 328/week @ 2023-11-01 243/week @ 2023-11-08 157/week @ 2023-11-15

1,156 downloads per month
Used in 2 crates

CC0 license

1.5K SLoC


crates.io docs.rs dependencies actively developed issues

pea2pea is a simple, low-level, and customizable implementation of a TCP P2P node.

The core library only provides the most basic functionalities like starting, ending and maintaining connections; the rest is up to a few low-level, opt-in protocols:

  • Handshake requires connections to adhere to the given handshake logic before anything else can be done with them
  • Reading enables the node to receive messages based on the user-supplied Decoder
  • Writing enables the node to send messages based on the user-supplied Encoder
  • OnDisconnect makes the node perform specified actions whenever a connection with a peer is severed
  • OnConnect makes the node perform specified actions whenever a connection with a peer is fully established (post-handshake)


  • small, simple, non-framework codebase: the entire library is ~1k LOC and there are few dependencies
  • ease of use: few objects and traits, no "turboeels" or generics/references that would force all parent objects to adapt
  • correctness: builds with stable Rust, there is no unsafe code, there's more code in tests than in the actual library
  • low-level: the user has full control over all connections and every byte sent or received
  • good performance: over 10GB/s in favorable scenarios, small memory footprint

how to use it

  1. define a clonable struct containing a Node and any extra state you'd like to carry alongside it
  2. implement the trivial Pea2Pea trait for it
  3. make it implement any/all of the protocols
  4. create that struct (or as many of them as you like)
  5. enable the protocols you'd like them to utilize

That's it!


  • including noise encryption, simple interop with libp2p, or TLS connections


  • all the desired functionalities are complete
  • the crate follows semver, and some API breakage is still possible before 1.0
  • the project is actively developed, with all changes being recorded in the CHANGELOG
  • some of the desired features that are not yet available in Rust include associated type defaults
  • the project aims to always build with the current stable Rust compiler; legacy version support is not a goal, but they might also work


~147K SLoC