parity selfdestruct traces are inserted out of order #162
Comments
mattsse
pushed a commit
that referenced
this issue
Jul 23, 2024
The `suicide`/`selfdestruct` trace should not be immediately after the parent trace but after all of the parent's subtraces. This can be fixed by ordering the `traces` using the attribute `trace_address` inside. closes #162
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
paradigmxyz/reth#9142
we don't record selfdestructs as individual trace nodes instead the node can have a selfdestruct state.
we compute the traceAddress correctly
but they get inserted incorrectly, right after the top-level call:
https://github.com/paradigmxyz/evm-inspectors/blob/b9850ffe4d67aadc46cba5e3798bee459a01a560/src/tracing/builder/parity.rs#L238-L256
TODO
The text was updated successfully, but these errors were encountered: