Max Inden
Max Inden
# Description In preparation for https://github.com/libp2p/rust-libp2p/pull/2751. ## Change checklist - [x] I have performed a self-review of my own code - [x] I have made corresponding changes to the documentation...
# Description Test that `HandlerWrapper` upholds the provided `max_negotiating_inbound_streams` limit. ## Links to any relevant issues Feature introduced in #2697. ## Open Questions ## Change checklist - [x] I have...
## Description In order to answer questions like: - Do most of the connections to remote peers use IPv4 or IPv6? TCP, Quic or WebRTC? ... - What protocols do...
# Description Add document outlining a set of coding guidelines followed and to be followed across the rust-libp2p code base. My goal is not to impose these guidelines onto anyone,...
## Description Enable users to provide a [Noise Prologue](https://noiseprotocol.org/noise.html#prologue) via [Builder::prologue](https://docs.rs/snow/latest/snow/struct.Builder.html#method.prologue). ## Motivation Needed for https://github.com/libp2p/rust-libp2p/pull/2622, more specifically to validate the remote's TLS fingerprints. See https://github.com/libp2p/specs/pull/412#discussion_r930582351. ## Requirements ## Open...
# Description This pull request does two things: 1. Remove support for `NetworkBehaviourEventProcess`. I am of the opinion that `NetworkBehaviourEventProcess` is not worth the complexity, especially for newcomers. I am...
## Description Expose the time it takes to establish an inbound or outbound connection. ## Motivation Needed for monitoring purposes, e.g. to be exposed to Prometheus via `libp2p-metrics`. Especially relevant...
## Description To combine two `NetworkBehaviour` implementations `libp2p-swarm` should provide a combinator. Contrary to [`NetworkBehaviour` implementation of `Either`](https://github.com/libp2p/rust-libp2p/blob/master/swarm/src/behaviour/either.rs) both `NetworkBehaviour` implementations would be running concurrently. ## Motivation One use-case is...
## Description Today there is no way to send generic local and remote node information from one `NetworkBehaviour` to another `NetworkBehaviour`, apart from `NetworkBehaviour::inject_new_external_addr`. Examples of such generic information could...
## Description Consider using https://github.com/rust-lang/rust-semverver to enforce semantic versioning. Instructions on how to integrate semverver in CI can be found on https://github.com/rust-lang/rust-semverver#ci-setup. ## Motivation Complying with Semver makes it easier...