Repository navigation
Trace Optimism post-exec transactions - #92
Merged
sduchesneau merged 3 commits intoNov 10, 2026
Merged
Conversation
The node still stops: dropping the transaction would emit a block that differs from the chain, and failing execution would reject a valid block.
firehose-tracer 5.5.1 adds the post-exec transaction type (0x7d), so the mapper no longer stops the node on it.
sduchesneau
marked this pull request as ready for review
November 10, 2026 20:45
This was referenced Nov 16, 2026
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.
Makes OP post-exec transactions (type
0x7D,OpTxEnvelope::PostExec, turned on by the Lagoon fork) traceable, and names the transaction when a type still cannot be traced.firehose-tracergoes to 5.5.1, which addsTxType::OptimismPostExec(TRX_TYPE_OPTIMISM_POST_EXEC = 125, Release 5.5.1 with Optimism post-exec transactions evm-firehose-tracer-rs#44). The mapper'stry_intonow maps0x7Dto it; a unit test covers it.f5c42840d1onrelease/base-2.x.This builds once
firehose-tracer5.5.1 is published. Then update the lock withcargo update -p firehose-tracer --precise 5.5.1(a plain update would pick 5.7.0). Verified against the 5.5.1 branch through a local[patch.crates-io]:cargo check -p reth-firehoseandcargo test -p reth-firehose --libpass.A post-exec transaction runs no EVM code, so its trace has no calls and, like any transaction without a call, no receipt and status
UNKNOWN.