debug_traceBlockByNumber returns error for a block with a failed transaction

hello, one of the teams developing on TAC reported they are getting error `{“id”:1,“jsonrpc”:“2.0”,“result”:[{“error”:“rpc error: code = Internal desc = failed to commit stateDB: failed to set account: failed to burn coins from account in bank wrapper: spendable balance 490550000000000000utac is smaller than 1000000000000000000utac: insufficient funds”}]}` when they’re executing `debug_traceBlockByNumber` for block `2341409` on our mainnet, the method works for other blocks.

link to explorer: https://explorer.tac.build/block/0x0a22606aef664096c0c518bdfab0d317205ae71647e075c4815ec1a49827e26c?tab=index

as seen in the explorer link, there was 1 EVM tx at that height that failed with the same error returned by the debug_trace endpoint, so it seems like a bug where the trace_debug endpoints throws an error for a block with failed tx instead of returning a trace.

do you think there’s any reason behind that and more importantly if there’s a fix for this?

here’s info for tac mainnet in case you need it for debugging:
- tacchain binary: https://github.com/TacBuild/tacchain/releases/tag/v1.0.1
- our evm fork: https://github.com/TacBuild/evm/tree/release/v0.1.x-tac
- rpc you can use to reproduce: https://rpc.tac.build
- cmd: `curl -X POST 'https://rpc.tac.build' -H 'Content-Type: application/json' -d '{"jsonrpc":"2.0","method":"debug_traceBlockByNumber","params":["0x23BA21"],"id":1}'`