-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: migrate to new inspector API #11
Conversation
@mattsse didn't you need the call/create inputs in Inspector |
I think we only need this for the foundry cheatcodes inspector, |
@@ -15,7 +17,7 @@ pub use maybe_owned::MaybeOwnedInspector; | |||
/// - Block: Hook on block execution | |||
/// - BlockWithIndex: Hook on block execution transaction index | |||
/// - Transaction: Hook on a specific transaction hash |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
doc looks outdated/wrong
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, this was the case previously, tbh I don't know why this is here.
Perhpas the idea was to move the stack from foundry to here, but I'd rather delete this one here, will probably do so.
Bumped to newest revm on |
lgtm |
will merge after CI |
this is a leftover of #11 @rakita the `output` of `CreateOutcome` is the runtime bytecode, right? https://github.com/paradigmxyz/evm-inspectors/blob/05352cd16db13fd89e9a974487b456e3f1498c69/src/tracing/types.rs#L48-L50
Closes #2
Blocked by reth migration
and
bluealloy/revm#1001