Sally MacFarlane

so you would get a message with the invalid call eg `2023-01-18 12:17:15.406+10:00 | vert.x-worker-thread-15 | DEBUG | JsonRpcExecutor | JSON-RPC request -> eth_call [{"data":"0x6d4ce63clkj","to":"0x9a3DBCa554e9f6b9257aAa24010DA8377C57c17e","gas":"0x2faf080"},"latest",null]`

please note with https://github.com/hyperledger/besu/pull/4965 the default max batch size changes to 1, you can increase this using the CLI option if required.

@samsondav Could you try to reproduce it with the latest release that's coming out soon? V.23.1.0.?

recent AT fail with invalid params - might be a clue https://app.circleci.com/pipelines/github/hyperledger/besu/22285/workflows/dad5b738-a624-4db5-8a90-1a7c8c304019/jobs/138045/tests - possibly related to exception handling, with invalid params used as default error typoe

Further improved by https://github.com/hyperledger/besu/pull/6143

@panicstyle we have made improvements to peering (among other things) in later besu versions. Are you able to try with latest besu? blockperiod 1s might be too short? did you...

Created #4987 for the remaining getUncle difference.

this has been implemented in a different PR

@daniellehrner can you take a look at this proposed fix - using streams instead of lists - https://github.com/dhallatmaine/besu/commit/af5ecc5f424acf6c5536c6805f37bc792e46ef16

This PR filters the DNS refresh messages (they come from tuweni) https://github.com/hyperledger/besu/pull/4155/files