feat: Add debug_traceTransaction migration support for historical backend#153
Draft
feat: Add debug_traceTransaction migration support for historical backend#153
Conversation
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.
Background
During the migration from Erigon to op-geth, the new node only stores data after the migration block, while historical data remains on the Erigon node. The
debug_traceTransactionRPC method was not forwarding requests to the historical backend, causing failures when tracing transactions that occurred before the migration block.Solution
Implemented hybrid routing for
debug_traceTransactionfollowing the LOCAL strategy pattern:GetBackend()method ineth/tracers/api.goto allow precise transaction existence checksXlayerHybridTracersAPIwrapper that:GetCanonicalTransactionWrapAPIsForXlayerto handledebugnamespace APIs