Show the crate…

3 unstable releases

0.28.0 Mar 12, 2021
0.27.1 Apr 3, 2021
0.27.0 Apr 2, 2021
0.0.0 Mar 11, 2021

#4 in #tetsy-libp2p

Download history 107/week @ 2024-03-03 142/week @ 2024-03-10 144/week @ 2024-03-17 181/week @ 2024-03-24 206/week @ 2024-03-31 91/week @ 2024-04-07 140/week @ 2024-04-14 142/week @ 2024-04-21 140/week @ 2024-04-28 120/week @ 2024-05-05 128/week @ 2024-05-12 119/week @ 2024-05-19 126/week @ 2024-05-26 108/week @ 2024-06-02 76/week @ 2024-06-09 123/week @ 2024-06-16

456 downloads per month
Used in 75 crates (10 directly)

MIT license

11K SLoC


High level manager of the network.

A Swarm contains the state of the network as a whole. The entire behaviour of a tetsy-libp2p network can be controlled through the Swarm. The Swarm struct contains all active and pending connections to remotes and manages the state of all the substreams that have been opened, and all the upgrades that were built upon these substreams.

Initializing a Swarm

Creating a Swarm requires three things:

  1. A network identity of the local node in form of a PeerId.
  2. An implementation of the Transport trait. This is the type that will be used in order to reach nodes on the network based on their address. See the transport module for more information.
  3. An implementation of the NetworkBehaviour trait. This is a state machine that defines how the swarm should behave once it is connected to a node.

Network Behaviour

The NetworkBehaviour trait is implemented on types that indicate to the swarm how it should behave. This includes which protocols are supported and which nodes to try to connect to. It is the NetworkBehaviour that controls what happens on the network. Multiple types that implement NetworkBehaviour can be composed into a single behaviour.

Protocols Handler

The ProtocolsHandler trait defines how each active connection to a remote should behave: how to handle incoming substreams, which protocols are supported, when to open a new outbound substream, etc.


~305K SLoC