-
Notifications
You must be signed in to change notification settings - Fork 361
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
Support for EIP-5656 and EIP-1153 #277
Comments
#278 adds support for EIP-1153 |
#279 adds support for EIP-5656 |
Awesome! Thank so much @RomarQ for taking the time to implement the two EIPs. We're also considering moving from this package to https://github.com/bluealloy/revm - but it's important that both have support for these new opcodes. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As of Solidity 0.8.25 on 14th March 2024 the default Ethereum hardfork is Dencun, meaning these new opcodes are emitted when the optimizer deems suitable.
MCOPY
opcode to the code base. Currently, copying memory requires developers to use two opcodes (MSTORE
andMLOAD
) and costs at least 96 gas. WithMCOPY
, it only costs around 26 gas. This improvement makes smart contracts more efficient with zero trade-offs.TLOAD
andTSTORE
opcodes to enable transient storage or medium-term memory for communication within complex transactions. This means the memory will be accessible to all function calls within the transaction and will be cleared once it’s completed.This means projects using this EVM implementation will revert due to invalid opcodes with many contracts that are compiled with the 0.8.25 release of Solidity and it's something that should be supported with high priority.
The text was updated successfully, but these errors were encountered: