-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
chore: Upgrade revm
#5502
chore: Upgrade revm
#5502
Conversation
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.
need to check, new revm api.
in the meantime please remove trailing ;
inputs: &mut CallInputs, | ||
) -> (InstructionResult, Gas, Bytes) { | ||
) -> Option<(InterpreterResult, Range<usize>)> { |
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.
this api is kinda weird
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 I'm not convinced the ranges being passed are correct, just 0..0
atm to placehold... Need to read into what it signifies
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.
Return struct should definitely be added, Range represents output place to the memory (where to write it).
Option is there if we want to short circuit the call and immediately return.
I talked with @mattsse and I feel that a better solution is to freeze revm version inside reth, and just cherry-pick needed commits. This would skip this additional work on integration of breaking changes.
Overview
Upgrades
revm
to the head commit (as of Nov 20, 2023), which includes theCanyon
hardfork definition.Metadata
closes #5490