mirror of
https://gitlab.com/pulsechaincom/erigon-pulse.git
synced 2025-01-03 09:37:38 +00:00
d20de9508e
When we call the debug_traceXXX API provided by Erigon, the withLog option in tracerConfig is very helpful. However, currently, the tracer cannot guarantee that the order of logs output is consistent with the event logs returned in the transaction receipt. This may make it difficult to use the output of the APIs. If you need to access event logs in order, it is recommended to use the event logs returned in the transaction receipt. Here is an example to illustrate the reason why the order of callTracer logs and receipt eventlogs can be inconsistent: In a call trace tree, if a call has multiple logs and this call has multiple child calls, and logs are also output in the child calls, the logs of the child calls may be output between the logs of the parent call in receipt. I add an index field of log to identify log index of the logs in tracer result, and it helps me a lot. |
||
|---|---|---|
| .. | ||
| 4byte.go | ||
| call.go | ||
| gen_account_json.go | ||
| gen_callframe_json.go | ||
| mux.go | ||
| noop.go | ||
| prestate.go | ||
| tracer.go | ||