ljedrz

Resolve the addresses for the purposes of handle_disconnect

1

This is a simple bugfix: the address provided in `Disconnect::handle_disconnect` is always the _true_ connected address, so it potentially (i.e. in case of inbound connections) needs to be resolved to...

Allow the node to start listening at any given time

2

This PR allows the node to begin listening for connection requests at a specified point in time (rather than at the point of creation of `Tcp`), allowing it to have...

A few things I've noticed while looking into other issues; each commit is self-contained and describes the specific change.

If we're confident that https://github.com/AleoHQ/snarkOS/pull/2168 solved the issue of missing calls to `Disconnect::handle_disconnect`, we can now remove this duplicate cleanup call. Closes #2102.

Many objects in the `Router` contain numerous `Arc`s to allow cloning; however, those objects are never cloned individually (only as part of the entire `Router`), so there is no need...

Just a routine update of dependencies to squash the pending dependabot PRs. note: this PR contains an update of snarkVM to `0.9.11`.

Correctly resolve addresses when calling Router::disconnect directly

2

While looking into potentially introducing strong typing to avoid IP addresses from being mixed up (though that would be a large change, so it might need to wait), I found...

## 💥 Proposal The current snarkOS handshake works roughly as follows: 1. the initiator connects to the responder 2. both send the challenge request 3. both verify the received challenge...

As suggested in https://github.com/seanmonstar/warp/issues/1012.

REST rate limiting

12

This PR introduces a rate limiting service (with a limit of 5 reqs/s) to the REST server.