Show the crate…

3 releases

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

#10 in #tetsy-libp2p

Download history 158/week @ 2024-08-26 77/week @ 2024-09-02 85/week @ 2024-09-09 100/week @ 2024-09-16 141/week @ 2024-09-23 93/week @ 2024-09-30 14/week @ 2024-10-07 64/week @ 2024-10-14 96/week @ 2024-10-21 57/week @ 2024-10-28 63/week @ 2024-11-04 39/week @ 2024-11-11 68/week @ 2024-11-18 101/week @ 2024-11-25 144/week @ 2024-12-02 164/week @ 2024-12-09

478 downloads per month
Used in 90 crates (25 directly)

MIT license

550KB
9K SLoC

tetsy-libp2p-core

Transports, upgrades, multiplexing and node handling of tetsy-libp2p.

The main concepts of tetsy-libp2p-core are:

  • A PeerId is a unique global identifier for a node on the network. Each node must have a different PeerId. Normally, a PeerId is the hash of the public key used to negotiate encryption on the communication channel, thereby guaranteeing that they cannot be spoofed.
  • The Transport trait defines how to reach a remote node or listen for incoming remote connections. See the transport module.
  • The StreamMuxer trait is implemented on structs that hold a connection to a remote and can subdivide this connection into multiple substreams. See the muxing module.
  • The UpgradeInfo, InboundUpgrade and OutboundUpgrade traits define how to upgrade each individual substream to use a protocol. See the upgrade module.

lib.rs:

Transports, upgrades, multiplexing and node handling of libp2p.

The main concepts of tetsy-libp2p-core are:

  • A PeerId is a unique global identifier for a node on the network. Each node must have a different PeerId. Normally, a PeerId is the hash of the public key used to negotiate encryption on the communication channel, thereby guaranteeing that they cannot be spoofed.
  • The Transport trait defines how to reach a remote node or listen for incoming remote connections. See the transport module.
  • The StreamMuxer trait is implemented on structs that hold a connection to a remote and can subdivide this connection into multiple substreams. See the muxing module.
  • The UpgradeInfo, InboundUpgrade and OutboundUpgrade traits define how to upgrade each individual substream to use a protocol. See the upgrade module.

Dependencies

~10–16MB
~298K SLoC