Replies: 2 comments
-
|
cc @canepat |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I understand the benefits of this proposal. However, some custom opt-in flag e.g. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Request
trace_callMany currently returns execution traces only; event logs are not included at all. Please add event logs to the per-call result so each item includes both the trace and the emitted logs—without requiring any extra flags.
Why this matters
When analyzing batches of calls, logs are indispensable for:
Right now, to get logs we must either fetch them separately or call debug_traceCall per item—both are inefficient for large batches.
Proposal
Extend trace_callMany response objects to include a logs array (same shape as eth_getTransactionReceipt.logs). Always return logs for each call (no opt-in flag). Preserve canonical ordering and fields (address, topics, data, blockNumber, transactionHash, logIndex, etc.).
Beta Was this translation helpful? Give feedback.
All reactions