Matthias Seitz

tracking issue the merge and afterwards

1

- [ ] rinkeby will be deprecated, currently, some tests use rinkeby -> move to goerli? - [ ] [changing APIs](https://docs.alchemy.com/reference/ethereum-developer-guide-to-the-merge#what-apis-are-changing): add `safe` + `finalized` to `BlockNumber`

feat: add WsServer handle

1

## Motivation provide a way to retrieve the spawned `WsServer` on error ## Solution Add `WsServerHandle` type that wraps the `JoinHandle` for the spawned `WsServer`. `WsServer` -> into_future -> WsServerFuture...

## Motivation also tested the sync vs. par file reading on solmate which has 50 source files in range of >4kb and par is only marginally faster: ```console read solmate/sequential...

## Motivation previously resolving the dependency graph was implemented sequentially This resolves all dependencies in parallel ## Solution use rayon + locks to guard the relevant maps for every new...

Add gas limit check when inserting new transactions

3

ensure requested gas limit < block.gaslimit: ref https://github.com/foundry-rs/reth/pull/71#discussion_r995863539 part of #36

### Describe the feature replace blind spawning and JoinSet with `TaskExecutor` ### Additional context _No response_

- [ ] add config option for blocking IPs in order to reject incoming connections - [ ] add peerId blocklist

ref https://github.com/foundry-rs/reth/pull/319 - [ ] add separate config option, like bootnodes, but nodes that we always want to connect to.

- [ ] Add options to `NetworkConfig` So that we can easily configure different networks etc. https://github.com/foundry-rs/reth/blob/5c8b64a6cbda63df3b8b2c4ec3ced06c1a7b361b/crates/net/network/src/session/mod.rs#L109-L113

The response objects used by the client types should include the peer that sent this message, so it can be reported if the message was bad.