2025 12 22 deps

[thedavidmeister]

Motivation

Solution

Checks

By submitting this for review, I'm confirming I've done the following:

• made this PR as small as possible
• unit-tested any new functionality
• linked any relevant issues or PRs
• included screenshots (if this involves a front-end change)

Summary by CodeRabbit

• Chores
  • Updated EVM compiler target version to enable support for the latest Ethereum protocol features.
  • Updated dependencies to the latest compatible versions for improved stability and compatibility.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

The pull request updates the EVM compilation target version from "paris" to "cancun" in the project configuration and advances the lib/rain.interpreter.interface submodule pointer to a newer commit reference.

Changes

Cohort / File(s)	Change Summary
Configuration foundry.toml	Updated evm_version from "paris" to "cancun"
Dependencies lib/rain.interpreter.interface	Advanced submodule commit pointer from f777a1c769433fb63dafe51db783bc64e001a0be to 2d06b797698d3ed2555e93162176479127a02b1a

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Single-line configuration change with no semantic complexity
• Submodule pointer update with no visible code modifications in the diff

Possibly related PRs

• 2025 06 01 update #34: Modifies both foundry.toml (evm_version) and the lib/rain.interpreter.interface submodule pointer, making it directly relevant.
• int #43: Updates the same lib/rain.interpreter.interface submodule pointer, advancing its commit reference forward.
• 2025 10 08 int bump #42: Also updates the lib/rain.interpreter.interface submodule pointer as part of dependency management.

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title '2025 12 22 deps' is vague and generic, using a date format and abbreviated term 'deps' without clearly conveying what dependency changes were made or why.	Provide a more descriptive title that explains which dependencies were updated and the rationale (e.g., 'Update EVM target version to cancun and pin interpreter interface submodule').

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch 2025-12-22-deps

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b07f073 and 92b7fb4.

⛔ Files ignored due to path filters (1)

• foundry.lock is excluded by !**/*.lock

📒 Files selected for processing (2)

• foundry.toml
• lib/rain.interpreter.interface

🔇 Additional comments (1)

foundry.toml (1)

24-24: Verify compilation and tests pass with Cancun EVM.

Updating from Paris to Cancun EVM introduces new opcodes and behavior changes. Ensure the codebase compiles successfully and all tests pass with the Cancun target before merging.

Note: No SELFDESTRUCT usage was found in the codebase, so EIP-6780 behavior changes do not apply here.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

❓ Verification inconclusive

Script executed:

# Check repository structure and submodule information
echo "=== Repository structure ==="
git ls-files lib/rain.interpreter.interface

echo -e "\n=== Submodule status ==="
git config --file .gitmodules --get-regexp path

echo -e "\n=== Check submodule file content ==="
cat lib/rain.interpreter.interface 2>/dev/null || echo "File not found or not a regular file"

echo -e "\n=== List files in lib directory ==="
ls -la lib/

Repository: rainlanguage/rain.orderbook.interface

---

Repository: rainlanguage/rain.orderbook.interface
Exit code: 0

stdout:

=== Repository structure ===
lib/rain.interpreter.interface

=== Submodule status ===
submodule.lib/rain.interpreter.interface.path lib/rain.interpreter.interface

=== Check submodule file content ===
File not found or not a regular file

=== List files in lib directory ===
total 0
drwxr-xr-x 3 jailuser jailuser  60 Dec 22 18:11 .
drwxr-xr-x 7 jailuser jailuser 340 Dec 22 18:11 ..
drwxr-xr-x 2 jailuser jailuser  40 Dec 22 18:11 rain.interpreter.interface

---

Script executed:

# Get git submodule commit information
echo "=== Git submodule status ==="
git submodule status lib/rain.interpreter.interface

echo -e "\n=== Check foundry.toml file ==="
if [ -f foundry.toml ]; then
  cat foundry.toml
else
  echo "foundry.toml not found"
fi

echo -e "\n=== Check PR description (git log) ==="
git log --oneline -5

echo -e "\n=== Check current git status ==="
git status --short

Repository: rainlanguage/rain.orderbook.interface

---

Repository: rainlanguage/rain.orderbook.interface
Exit code: 0

stdout:

=== Git submodule status ===
-2d06b797698d3ed2555e93162176479127a02b1a lib/rain.interpreter.interface

=== Check foundry.toml file ===
[profile.default]
src = 'src'
out = 'out'
libs = ['lib']

# See more config options https://github.com/foundry-rs/foundry/tree/master/config

solc = "0.8.25"

# Try to make sure the optimizer doesn't touch the output in a way that can break
# source maps for debugging.
# via_ir = false
# optimizer = false
# optimizer_runs = 0
# optimizer_steps = 0

# These settings should be used for snapshots
optimizer = true
optimizer_runs = 1000000

bytecode_hash = "none"
cbor_metadata = false

evm_version = "cancun"

remappings = [
  "rain.math.float/=lib/rain.interpreter.interface/lib/rain.math.float/src/"
]

[fuzz]
runs = 2048
=== Check PR description (git log) ===
92b7fb4 cancun

=== Check current git status ===

---

Script executed:

# Check .gitmodules to understand the submodule
echo "=== .gitmodules content ==="
cat .gitmodules

echo -e "\n=== Check git log for context of recent changes ==="
git log --oneline -10

echo -e "\n=== Show the most recent commit details ==="
git show --name-status -1

Repository: rainlanguage/rain.orderbook.interface

---

Repository: rainlanguage/rain.orderbook.interface
Exit code: 0

stdout:

=== .gitmodules content ===
[submodule "lib/rain.interpreter.interface"]
	path = lib/rain.interpreter.interface
	url = https://github.com/rainlanguage/rain.interpreter.interface

=== Check git log for context of recent changes ===
92b7fb4 cancun

=== Show the most recent commit details ===
commit 92b7fb476e8e17e82c001bde6c8c9b8770558bea
Author: thedavidmeister <thedavidmeister@gmail.com>
Date:   Mon Dec 22 22:10:04 2025 +0400

    cancun

A	.github/workflows/pr-assessment.yaml
A	.github/workflows/rainix.yaml
A	.gitignore
A	.gitmodules
A	LICENSE
A	LICENSES/CC0-1.0.txt
A	LICENSES/LicenseRef-DCL-1.0.txt
A	README.md
A	REUSE.toml
A	flake.lock
A	flake.nix
A	foundry.lock
A	foundry.toml
A	lib/rain.interpreter.interface
A	slither.config.json
A	src/interface/IOrderBookV5.sol
A	src/interface/IOrderBookV5ArbOrderTaker.sol
A	src/interface/IOrderBookV5OrderTaker.sol
A	src/interface/deprecated/v1/IOrderBookV1.sol
A	src/interface/deprecated/v2/IOrderBookV2.sol
A	src/interface/deprecated/v3/IOrderBookV3.sol
A	src/interface/deprecated/v3/IOrderBookV3ArbOrderTaker.sol
A	src/interface/deprecated/v3/IOrderBookV3OrderTaker.sol
A	src/interface/deprecated/v4/IOrderBookV4.sol
A	src/interface/deprecated/v4/IOrderBookV4ArbOrderTaker.sol
A	src/interface/deprecated/v4/IOrderBookV4OrderTaker.sol
A	src/interface/ierc3156/IERC3156FlashBorrower.sol
A	src/interface/ierc3156/IERC3156FlashLender.sol
A	src/interface/unstable/IOrderBookV6.sol
A	src/interface/unstable/IOrderBookV6ArbOrderTaker.sol
A	src/interface/unstable/IOrderBookV6OrderTaker.sol

---

Provide comprehensive PR description with rationale and EVM version verification.

The commit message "cancun" is insufficient context for this initial repository. This adds a critical dependency on rain.interpreter.interface and upgrades the EVM target to Cancun, both requiring clear explanation.

Please provide:

1. Rationale: Why is Cancun EVM targeted? Are there specific opcodes or features required?
2. Submodule verification: Confirm the rain.interpreter.interface commit 2d06b797698d3ed2555e93162176479127a02b1a is stable and tested.
3. Compatibility verification: Have you verified all Solidity contracts compile correctly with solc 0.8.25 and Cancun EVM?
4. Testing results: Provide evidence that unit and integration tests pass with this configuration.

[github-actions]

@coderabbitai assess this PR size classification for the totality of the PR with the following criterias and report it in your comment:

S/M/L PR Classification Guidelines:

This guide helps classify merged pull requests by effort and complexity rather than just line count. The goal is to assess the difficulty and scope of changes after they have been completed.

Small (S)

Characteristics:

• Simple bug fixes, typos, or minor refactoring
• Single-purpose changes affecting 1-2 files
• Documentation updates
• Configuration tweaks
• Changes that require minimal context to review

Review Effort: Would have taken 5-10 minutes

Examples:

• Fix typo in variable name
• Update README with new instructions
• Adjust configuration values
• Simple one-line bug fixes
• Import statement cleanup

Medium (M)

Characteristics:

• Feature additions or enhancements
• Refactoring that touches multiple files but maintains existing behavior
• Breaking changes with backward compatibility
• Changes requiring some domain knowledge to review

Review Effort: Would have taken 15-30 minutes

Examples:

• Add new feature or component
• Refactor common utility functions
• Update dependencies with minor breaking changes
• Add new component with tests
• Performance optimizations
• More complex bug fixes

Large (L)

Characteristics:

• Major feature implementations
• Breaking changes or API redesigns
• Complex refactoring across multiple modules
• New architectural patterns or significant design changes
• Changes requiring deep context and multiple review rounds

Review Effort: Would have taken 45+ minutes

Examples:

• Complete new feature with frontend/backend changes
• Protocol upgrades or breaking changes
• Major architectural refactoring
• Framework or technology upgrades

Additional Factors to Consider

When deciding between sizes, also consider:

• Test coverage impact: More comprehensive test changes lean toward larger classification
• Risk level: Changes to critical systems bump up a size category
• Team familiarity: Novel patterns or technologies increase complexity

Notes:

• the assessment must be for the totality of the PR, that means comparing the base branch to the last commit of the PR
• the assessment output must be exactly one of: S, M or L (single-line comment) in format of: SIZE={S/M/L}
• do not include any additional text, only the size classification
• your assessment comment must not include tips or additional sections
• do NOT tag me or anyone else on your comment

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Get all files changed in the PR to ensure we have the complete picture
git diff --name-only origin/main...HEAD

Length of output: 40

---

🏁 Script executed:

#!/bin/bash
# Check current branch and recent commits
git branch -a
echo "---"
git log --oneline -10
echo "---"
# Try to see what files changed
git diff --name-only HEAD~5..HEAD
echo "---"
# Check git status
git status

Length of output: 998

---

🏁 Script executed:

#!/bin/bash
# Check what changed in the specific commits for this PR
echo "=== Commit: ba33a9f update int ==="
git show --name-only --format="%s" ba33a9f
echo ""
echo "=== Commit: 92b7fb4 cancun ==="
git show --name-only --format="%s" 92b7fb4
echo ""
echo "=== Combined diff stats for this PR ==="
git diff --stat b07f073..92b7fb4

Length of output: 351

---

SIZE=S