Nounce too low error when tracing blocks.

[Mummyhap]

I hope the development team can optimize the debug_traceBlockBy* methods. The current issue is that when tracing a block, if there are failed transactions within the block, it returns a 'nonce too low' error, which prevents the trace results of other transactions from being returned.

To reproduce nonce too low, send this request:
{
"id": 1,
"jsonrpc": "2.0",
"method": "debug_traceBlockByNumber",
"params": [
"0x4C4B40C",
{
"tracer": "callTracer"
}
]
}

The return is:
{
"jsonrpc": "2.0",
"id": 1,
"error": {
"code": -32000,
"message": "nonce too low"
}
}

This makes it difficult to create the corresponding index database, as indexing blocks can intermittently return errors. We hope that after optimization, even if there are failed transactions within the block, the trace results of other successful transactions can still be returned.

[vegarsti]

@tungng98 Is there a plan to address this? 🙏🏻

[tungng98]

Thanks for posting the issue here. We acknowledged the the bug and pushed more resources for have this issue resolved ASAP.