Update to go-ethereum 1.12.0 #199
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
damilolaedwards
pushed a commit
that referenced
this pull request
Nov 16, 2023
* Updated CallMessage to be compliant with core.Message made in new go-ethereum --------- Co-authored-by: anishnaik <anish.r.naik@gmail.com>
s4nsec
pushed a commit
that referenced
this pull request
Jul 9, 2024
* Updated CallMessage to be compliant with core.Message made in new go-ethereum --------- Co-authored-by: anishnaik <anish.r.naik@gmail.com>
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.
This PR brings support for go-ethereum 1.12.0, courtesy of @anishnaik updating medusa-geth here and making the initial updates to medusa on this branch.
I've reviewed Anish's updates and made a rather minor fix for a minor chain revert issue that was caused by an earlier PR. After verifying the following, we can merge:
SourceMapdoes not encounter problems with introduction of thePUSH0instruction, as PUSH instructions must be specially considered when separating opcodes from operands. This just involves testing report generation with PUSH0 instructions.