-
Notifications
You must be signed in to change notification settings - Fork 0
update deps #14
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
Merged
Merged
update deps #14
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
Submodule openzeppelin-contracts
updated
920 files
Submodule rain.string
updated
5 files
| +12 −12 | .gas-snapshot | |
| +2 −2 | foundry.lock | |
| +1 −1 | foundry.toml | |
| +1 −1 | lib/openzeppelin-contracts | |
| +1 −1 | lib/rain.solmem |
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.
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.
🧩 Analysis chain
🏁 Script executed:
Repository: rainlanguage/rain.math.fixedpoint
Length of output: 355
🏁 Script executed:
Repository: rainlanguage/rain.math.fixedpoint
Length of output: 164
🏁 Script executed:
Repository: rainlanguage/rain.math.fixedpoint
Length of output: 548
🏁 Script executed:
Repository: rainlanguage/rain.math.fixedpoint
Length of output: 117
🏁 Script executed:
Repository: rainlanguage/rain.math.fixedpoint
Length of output: 112
🌐 Web query:
Solidity 0.8.25 default EVM version Cancun💡 Result:
Yes — Solidity v0.8.25 sets the compiler's default EVM version to "cancun". [1][2]
Note: later releases (e.g., v0.8.30) changed the default EVM version (to "prague"). [3]
Sources:
🌐 Web query:
Cancun EVM vs Paris breaking changes opcodes💡 Result:
Short comparison — Cancun (Dencun-era EVM changes) vs Paris (Merge) — focused on opcode breaking/added changes:
Paris (The Merge)
Cancun / Dencun (post‑Shanghai family)
Notes:
Sources:
[1] Coinbase explainer (Paris / PREVRANDAO).
[2] Ethereum roadmap / upgrade descriptions (Paris).
[3] Ethereum Execution Spec tests / changelog (Cancun, EIP‑1153 coverage).
[4] @ethereumjs/@evm and EIP listings (EIP‑1153 transient storage).
[5] Vyper release notes (MCOPY usage and Cancun evm target).
[6] Ethereum roadmap (Shanghai / PUSH0 context).
Verify Cancun EVM compatibility testing for submodules.
Solidity 0.8.25 does default to Cancun EVM. The three submodules (openzeppelin-contracts, rain.math.saturating, rain.string) are present in the repository. While the Paris-to-Cancun migration is relatively safe—Cancun introduced new opcodes (TSTORE, TLOAD, MCOPY) without breaking existing opcode semantics—it's appropriate to confirm the submodules and their dependencies compile and behave correctly under the Cancun EVM. Run the test suite with
forge test --evm-version cancun -vto verify bytecode generation and contract behavior.