-
Notifications
You must be signed in to change notification settings - Fork 649
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
EIP170 Contract Size Limit #1466
Comments
Yup a quick search shows that it is functioning correctly.
The change seems fine to me, I agree that it's at least a slight improvement. |
Might be good for us to write a non-JSON-fixture based test to test for this specific thing. We rely on the JSON-fixture tests for compliance with these things, but it'd be good to have a legible test as well (similar to what @cburgdorf has done for many of our opcodes). |
Would like to take a stab on this |
@pipermerriam , is the issue solved with the #1799 pull request? |
I dug into this issue. I have some thoughts about this. Please let me know if there are any mistakes.
|
What is wrong?
Double checking this is the intended functionality.
EIP170 states that the contract size limit was changed to
2**14 + 2**13
which is 24,576 bytes. The following line implementations the constant for EIP170, but it is off by one.py-evm/eth/vm/forks/spurious_dragon/constants.py
Line 13 in 0ff7bc0
How can it be fixed
Validate that the number is correctly applied. If it is, consider making the number match and modifying the condition that tests for it so that it works with the actual number described in EIP170.
The text was updated successfully, but these errors were encountered: