- Coverage
- 72.44%
205 out of 283 items documented1 out of 212 items with examples - Links
-
web3infra-foundation/libp2p-rs
164 24 0 - crates.io
- Dependencies
-
- asn1_der ^0.6.1 normal
- async-trait ^0.1 normal
- bs58 ^0.3.0 normal
- bytes ^0.5 normal
- ed25519-dalek ^1.0.0-pre.4 normal
- fnv ^1.0 normal
- futures ^0.3 normal
- futures-timer ^3 normal
- lazy_static ^1.2 normal
- libp2prs-multiaddr ^0.2.1 normal
- libp2prs-traits ^0.2.1 normal
- libsecp256k1 ^0.3.1 normal
- log ^0.4 normal
- multihash ^0.11.0 normal
- parking_lot ^0.10.0 normal
- pin-project ^0.4 normal
- prost ^0.6.1 normal
- rand ^0.7 normal
- ring ^0.16.9 normal
- rw-stream-sink ^0.2.0 normal
- salsa20 ^0.3.0 normal
- serde ^1.0.117 normal
- serde_json ^1.0.59 normal
- sha2 ^0.8.0 normal
- sha3 ^0.8 normal
- smallvec ^1.0 normal
- thiserror ^1.0 normal
- unsigned-varint ^0.3 normal
- zeroize ^1 normal
- libp2prs-runtime ^0.2.1 dev
- quickcheck ^0.9.0 dev
- prost-build ^0.6 build
- Versions
- Owners
-
Transports, upgrades, multiplexing and node handling of *libp2p*.
The main concepts of 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`] and [`Upgrader`] traits define how to upgrade each
individual substream to use a protocol.
See the `upgrade` module.