Fix: Document enableReturnData for debug trace methods

[alexandratran]

What should be changed?

Update the debug trace docs for the behavior merged in besu-eth/besu#10172.

The PR adds an optional enableReturnData boolean to TransactionTraceParams. The default is false. When set to true, Besu captures EVM return data per opcode and includes returnData in each applicable StructLog entry as a 0x-prefixed hex string. The field is omitted when return data isn't enabled, isn't captured, or is empty.

Suggested docs updates:

• Add enableReturnData to the options object for debug trace methods in docs/public-networks/reference/api/index.md.
• At minimum, update the methods called out by the PR and changelog: debug_traceTransaction and debug_traceBlockByNumber.
• Verify the shared TransactionTraceParams usage before updating related sections, including debug_traceCall, debug_traceBlock, debug_traceBlockByHash, and the standard trace-to-file debug methods.
• Update docs/public-networks/reference/api/objects.md to add returnData to the structured log object, with the omission behavior above.
• Consider adding or adjusting an example request that uses "enableReturnData": true and a response snippet that includes returnData.

Docs page

• https://besu.hyperledger.org/public-networks/reference/api/#debug_tracetransaction
• https://besu.hyperledger.org/public-networks/reference/api/#debug_traceblockbynumber
• https://besu.hyperledger.org/public-networks/reference/api/objects#structured-log-object

Issue type

• Outdated content
• Missing content

Source links

• feat(debug): add enableReturnData param and returnData field  besu#10172
• Related spec alignment: Standardize opcode tracer behavior for debug_traceBlockByNumber and debug_traceTransaction ethereum/execution-apis#762