Bor client not able to trace blocks by number

[ShisheerBitgo]

System information

Bor client version: v2.5.3

Heimdall client version: v0.5.2

OS & Version: Ubuntu 22.04

Environment: Polygon Amoy

Type of node: Archive

Additional Information: N/A

Overview of the problem

The debug_traceBlockByNumber call does not work if a block includes a StateSync transaction. I get an error instead of the trace.

Reproduction Steps

I run bor with the following arguments:

--datadir "/home/fullnode/data"
--port 30303
--http --http.addr '0.0.0.0'
--http.vhosts '*'
--http.corsdomain '*'
--http.port 8545
--ipcpath "/home/fullnode/data/bor.ipc"
--http.api 'debug,eth,net,web3,txpool,bor,admin'
--syncmode 'full'
--chain "amoy"
--gcmode "archive"
--ws --ws.port 8546 --ws.addr 0.0.0.0 --ws.origins '*'
--miner.gasprice "1000000000"
--miner.gaslimit '45000000'
--rpc.txfeecap 10
--txpool.nolocals
--txpool.accountslots 16
--txpool.globalslots "131072"
--txpool.accountqueue 64
--txpool.globalqueue 131072
--txpool.lifetime '1h30m0s'
--txpool.pricelimit "1"
--maxpeers "2000"
--maxpendpeers "500"
--metrics
--metrics.prometheus-addr "0.0.0.0:7071"
--bor.heimdall "http://heimdall-node:1317"
--bootnodes "enode://383ec39eb7f7e23538ea846f502602632110a6bcfc7521bfc2b8833f5a190779507d006b28650d83674b75d188cb36bcb3c3e168a0f2b3d98f9a651cc6603146@52.214.229.208:30303,enode://bce861be777e91b0a5a49d58a51e14f32f201b4c6c2d1fbea6c7a1f14756cbb3f931f3188d6b65de8b07b53ff28d03b6e366d09e56360d2124a9fc5a15a0913d@54.217.171.196:30303,enode://a4a387ad423a2fd0d652808b270082250d3c616b7e8537209584ebad4806dd50ef8dc66a371c85c7f55e6c1f53747edbb11055c8073cfacf312047eaeb328f58@54.171.220.164:30303,enode://4a3dc0081a346d26a73d79dd88216a9402d2292318e2db9947dbc97ea9c4afb2498dc519c0af04420dc13a238c279062da0320181e7c1461216ce4513bfd40bf@13.251.184.185:30303,enode://e8fe33b52f90d4bc7a4e75800945df449d1a091bd347c9f11cd1dbcd98ea28cb4c231cb3b1c6feacdabca2aa91f1a6744724b44edc9382c107968792abdef261@52.74.18.182:30303,enode://b240f1f18e8f3cc61df96a164ba215ea6fc3f00717e4300da6283362a0438bda53f81ecc24c575ff130066d42096319fa027c952681bbb4f003e0bdd5d5b4e61@52.76.37.145:30303,enode://de55d16b6e1fca28cdd3d11eb0dd89e3b77b96d4722172bd5e04ac255922324076a87748e97bc021af2307dccbb5ef8062389cfcba1845f77219eee7935dea9f@52.74.125.36:30303,enode://7f2272685fc3e31c8e43c7687dda43ea3192fd310ba01efcb7811d5dc7ad5a64402ea8cd827650e573a174cf29bb69331dffcca6f0b9894ef17eeafabd97a41d@47.128.184.10:30303,enode://c66e12243b425b63528dd8b1ce87f2f7fbc85f35485e2d8bf6bbf0ec0dcd05b3a582ef62daadbde061b58058735788335d09ed972a451242b9943b85d323c239@63.32.214.97:30303,enode://bd56c0f00dd37e14ae2b84f5eb50e357d3a2d326bdbb0cbb987411268b3f132288f6c86157fc132c6902d18b9be0de8bbdcd12d926e16232ebadd8e274aae780@52.208.81.179:30303,enode://2f015d5b1571165975382281a2117a9b514e1b38e87a8116596fc9b3b121a93cfb238eb6f7b3ae30cf9c0154384372745ce9edc09cbc30526ab7e2059f57ddee@54.74.160.230:30303"
--discovery.dns "enrtree://AKUEZKN7PSKVNR65FZDHECMKOJQSGPARGTPPBI7WS2VUL4EGR6XPC@amoy.polygon-peers.io"
--snapshot=false
--cache="8192"
--db.engine="pebble"
--state.scheme="hash"

I then make this request to my node:

curl --location 'localhost:8545' \
--header 'Content-Type: application/json' \
--data '{
    "jsonrpc": "2.0",
    "method": "debug_traceBlockByNumber",
    "params": [
        "0x1bc34e0",
        {
            "tracer": "callTracer"
        }
    ],
    "id": 3
}'

Logs / Traces / Output / Error Messages

I get this response:

{
    "jsonrpc": "2.0",
    "id": 3,
    "error": {
        "code": -32000,
        "message": "max fee per gas less than block base fee: address 0x0000000000000000000000000000000000000000, maxFeePerGas: 0, baseFee: 63"
    }
}

NOTE: This happens with other blocks too. For example, 0x1c81800 and 0x1c911f0

Additional Information

N/A

[lcmmhcc]

I got the same problem using QUIKNODE RPC.