Add option to use native tracer in replay #84
Merged
Conversation
This file contains 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
Handle EVM calls in the traces and encode binary data as hex.
rauljordan
approved these changes
Aug 20, 2024
rauljordan
reviewed
Aug 20, 2024
| } | ||
|
|
||
| #[test] | ||
| fn parse_call() { |
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.
Description
We developed a native Go tracer in Nitro to be used in Cargo Stylus Replay (OffchainLabs/nitro#2560). During this process, we also improved the JS tracer to be compatible with the native one. This PR adds those improvements to the JS tracer in Stylus Replay and a CLI option for using the native tracer. The native tracer won't be enabled by default because it isn't released yet. We can deprecate the JS tracer once the native tracer is released and proven to work correctly.
Checklist