-
Notifications
You must be signed in to change notification settings - Fork 285
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
EIP-3860: Limit and meter initcode #525
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## instr_create #525 +/- ##
================================================
- Coverage 97.45% 97.40% -0.06%
================================================
Files 62 63 +1
Lines 5980 6047 +67
================================================
+ Hits 5828 5890 +62
- Misses 152 157 +5
Flags with carried forward coverage won't be shown. Click here to find out more.
|
8381247
to
bdc62f1
Compare
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.
I'd add rule 3 here as well (before rule 4). I like to have "light" checks on the EVM side. This also helps against multiplication overflow. Any counter-arguments?
Initially I implemented rule 3 in evmone, but that deviates from geth's implementation ethereum/go-ethereum#23847 (see |
f2b318b
to
110bff5
Compare
I've updated this PR according to ethereum/EIPs#6040. |
725b28b
to
ed8a85d
Compare
The order of the checks in CREATE2 are going to change in the spec.
Implement EIP-3860. Co-authored-by: Paweł Bylica <[email protected]>
Co-authored-by: Paweł Bylica <[email protected]>
I messed up with GitHub here. Can you re-create the PR? |
Sure. Re-created as PR #545. |
EIP-3860 is included into Shanghai. This PR implements Rules 3 & 4 of the specification. Rules 1 & 2 should be implemented on the host side. See erigontech/silkworm#808 for an example of host implementation.