fix(tracer): backport revm inspector selfdestruct fix - #145
Merged
Conversation
Backport of bluealloy/revm#3805. The inspector could emit a SELFDESTRUCT callback built from an unrelated journal entry, so callTracer and trace_replayTransaction reported transfers that never happened. Execution, state and receipts are unaffected. Applied via [patch.crates-io] against hl-archive-node/revm@fdf9b16b. All revm crates are pinned together: revm-inspector depends on its siblings by path within the monorepo, so patching it alone pulls in duplicate copies and fails to compile.
sprites0
force-pushed
the
fix/revm-inspector-stale-selfdestruct
branch
from
July 25, 2026 21:21
b62e019 to
62d43c2
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport of bluealloy/revm#3805, applied via
[patch.crates-io]againsthl-archive-node/revm@fdf9b16b.The inspector could emit a SELFDESTRUCT callback built from an unrelated journal entry, so
callTracerandtrace_replayTransactionreported transfers that never happened. Execution, state and receipts are unaffected.cargo test -p revm-inspector --libon the fork: 17/17, including upstream's regression test.Note: This doesn't affect consensus.