debug_traceBlockByX response is missing txHash for trace entries

[jamesstanleystewart]

Hey Besu team. We attempted to use Besu for some debug_traceBlockByX calls today and noticed a difference from the geth implementation which I feel like could be a bug.
When tracing a transaction, both geth and besu return an object (which the besu docs call Trace object) like:

result: {
   gas: 85301,
   returnValue: "",
   structLogs: [{ ... }]
{

However, when tracing a block with debug_traceBlockByX geth returns an array of these transaction trace results, with a transactionHash for each as a reference like:

[
  {
    txHash: "0xabba...",
    result: {
      gas: 85301,
      returnValue: "",
      structLogs: [{ ... }]
    }
  },
  { txHash: "0xblah...", result: { ... } }
]

and Besu omits the txHash and result, just returning an array of Trace Object directly:

[
  {
      gas: 85301,
      returnValue: "",
      structLogs: [{ ... }]
  },
  { ... }
]

Wondering if there's a debug_* spec defined, or if its just up to the devs to decide the format they want to use. Having the txHash reference to associate the traces with each transaction in a block seems correct/useful to me.

Steps to Reproduce

1. [Step 1]
   curl localhost:8080 -X POST -H "Content-Type: application/json" -d '{"id": 1, "jsonrpc": "2.0", "method": "debug_traceBlockByNumber", "params": ["latest"]}' against Besu and Geth

Expected behavior: [What you expect to happen]
Geth and Besu return the same format for block tracing
Actual behavior: [What actually happens]
Besu has a differing format as described above

Frequency: [What percentage of the time does it occur?]
all the time :)

Versions (Add all that apply)

• Software version: the latest linea-besu-package in kubernetes on a i3en.xlarge