chore: Update libevm #1013
Merged
chore: Update libevm #1013
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
ARR4N
approved these changes
Jun 10, 2025
|
I'll cut a proper release soon. Just want to get one more PR in for SAE usage. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Why this should be merged
Firewood PR #959 requires an updated libevm branch to build.
How this works
Since ava-labs/libevm#187, libevm's main branch can be used in
go.modfiles with the cherry-picked commits. Uses ava-labs/avalanchego#4006How this was tested
CI
Need to be documented?
No
Need to update RELEASES.md?
No?