fix: enforce paris evm version #1211
Closed
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
|
question—is the IPC team planning to support Cancun evm compatibility? common tooling like openzeppling and foundry are now releasing tooling that uses Paris by default, so it requires a bit of vigilance to stay on top of it—which is easier for internal teams like Basin, but might be challenging for newcoming devs using Basin. note: our tests started failing when using the latest |
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.
The newest foundry nightly build now uses cancun as the default EVM version (foundry-rs/foundry#9131). This breaks everything in IPC because transient storage opcodes are not supported.