chore: update pectra system contracts bytecodes & addresses #1512
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
onbjerg
requested review from
DaniPopes,
gakonst,
mattsse,
prestwich and
emhane
as code owners
mattsse
approved these changes
Oct 18, 2024
onbjerg
force-pushed
the
onbjerg/pectra-bytecodes
branch
from
5f60265
to
3796d54
Compare
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.
Motivation
The bytecodes and addresses for some system contracts in Pectra were changed for devnet 4.
Solution
Update them accordign to the EIPs.
The runtime bytecodes were calculated by pasting the deployment code into evm.codes and copying the resulting contract 🙃
PR Checklist