trace_replayBlockTransactions response format

[cristian-dutu]

Reth version:

reth-ethereum-cli Version: 1.7.0-dev
Commit SHA: 4a05b101e0759038cb29b261595292532e582be2
Build Timestamp: 2025-12-05T15:07:49.444168797Z
Build Features: asm_keccak,jemalloc
Build Profile: maxperf

Start cmd:

ExecStart=/usr/local/bin/reth node \
    --chain=bsc \
    --db.max-size=8TB \
    --full \
    --datadir=/data/ \
    --authrpc.addr=0.0.0.0 \
    --authrpc.port=8551 \
    --http \
    --http.addr=0.0.0.0 \
    --http.api=eth,net,web3,txpool,debug,trace \
    --http.corsdomain='*' \
    -vvv \
    --color=never \
    --metrics=0.0.0.0:6060 \
    --engine.parallel-sparse-trie \
    --engine.memory-block-buffer-target=128 \
    --rpc.gascap=max \
    --rpc-cache.max-blocks=10000 \
    --rpc-cache.max-receipts=5000 \
    --rpc-cache.max-concurrent-db-requests=1024 \
    --txpool.gas-limit=36000000 \
    --rpc.txfeecap=0 \
    --rpc.max-connections=10000 \

Not sure if it's an issue or not, but the response format differs from erigon. Will this be the new format on traces?

request:

{
  "jsonrpc": "2.0",
  "id": 3,
  "method": "trace_block",
  "params": [
    "0x4353685"
  ]
}

[zlacfzy]

which erigon version do you use, it's not a issue

[cristian-dutu]

erigon- v1.4.2

Yeah not exactly an issue, was curious if this will remain in the current format.

[zlacfzy]

Do you have same case in testnet? I think it may not a format issue. erigon result means this tx create the account, but reth means before this tx the account already exist.