Chase
~~Chase from QuickNode here. Nethermind has the correct trace data, the output above is actually from OpenEthereum and this was my mistake. Very sorry.~~
Correction, this IS Nethermind. I got my nodes mixed up. It's happening on both `Nethermind/v1.13.3-0-0e3289f55-20220624/X64-Linux/6.0.6` And `Nethermind/v1.13.1-0-155ca7ad0-20220624/X64-Linux/6.0.5`
Still happening 1.14.1
No, it looks like I built off `master` - what branch or release should I be working off? `develop`? `v0.23.7.0-alpha`? What is the ideal candidate for a DAppNode package release?
If you copy #103 with the right chain info for BSC, it should work...
``` --rpc.accessList=/home/eth/rules.json cat /home/eth/rules.json { "allow": [ "web3_clientVersion", "web3_sha3", "net_listening", "net_peerCount", "net_version", "eth_blockNumber", "eth_chainID", "eth_chainId", "eth_protocolVersion", "eth_syncing", "eth_gasPrice", "eth_maxPriorityFeePerGas", "eth_feeHistory", "eth_getBlockByHash", "eth_getBlockByNumber", "eth_getBlockTransactionCountByHash", "eth_getBlockTransactionCountByNumber", "eth_getUncleByBlockHashAndIndex", "eth_getUncleByBlockNumberAndIndex", "eth_getUncleCountByBlockHash", "eth_getUncleCountByBlockNumber", "eth_getTransactionByHash", "eth_getRawTransactionByHash",...
Is anyone having issues using debug_traceCall with archive blocks? I'm getting: ``` {"jsonrpc":"2.0","id":1,"result":null,"error":{"code":-32000,"message":"block 18992271(9c7cb3118bc32a473de8ed2cc98d8a3ba7e616a518db75b2beaa483dc2823809) not found"}} ``` But the block is available via `eth_getBlockByNumber` on `2022.07.3` This is with BSC...
Still a feature request