Sally MacFarlane

https://github.com/hyperledger/besu/issues/4504 Another is for `eth_getProof` besu has key 0x1 and geth has 0x01

https://github.com/hyperledger/besu/issues/4505 And for `eth_getTransactionReceipt` geth has an extra field `type`

This one is interesting - tx not processed because of gas price ``` >> {"jsonrpc":"2.0","id":27,"method":"eth_sendRawTransaction","params":["0xf86303018261a894aa000000000000000000000000000000000000000a825544820a95a0487f7382a47399a74c487b52fd4c5ff6e981d9b219ca1e8fcb086f1e0733ab92a063203b182cd7e7f45213f46e429e1f5ab2a5660a4ed54b9d6ee76be8d84d5ca8"]}

those under `rpc` seem to all fail with the error `could not fund account` eg https://hivetests2.ethdevops.io/?page=v-pills-results-tab&suite=1665365843-7723b6f8498880db60b6c679527e30b2.json

Thanks for reporting this @estensen - this one sounds like a "this should never happen" - will investigate

Hi - in 22.7.2 we changed the logging of this message - so the stacktrace goes to DEBUG level log as per https://github.com/hyperledger/besu/pull/4334 - it's usually not something that will...

@estensen any further updates on this?

Yeah you can use a custom log4j config file as per https://besu.hyperledger.org/en/stable/public-networks/how-to/monitor/logging/?h=log4j#advanced-logging There's an example here that tunes logging for various packages https://github.com/lucassaldanha/besu-local-nodes/blob/master/config/besu/log4j.xml

Are you using latest lighthouse version? Also Besu 22.7.5 ?

failed because of hsqldb https://nvd.nist.gov/vuln/detail/CVE-2022-41853 latest version of hsqldb does not resolve it: hsqldb-2.7.0.jar (pkg:maven/org.hsqldb/[email protected]) : CVE-2022-41853