feat!(rust): upgrade alloy-evm to 0.30.0, bump reth to 082c36e, remove op feature

[theochap]

Summary

• Upgrade alloy-evm from 0.27.2 to 0.30.0 and bump alloy-op-evm to 0.30.0
• Bump reth from v1.11.3 / f0d07c3 to 082c36e (uses reth-rpc-traits from crates.io)
• Bump revm 34 → 36, op-revm 15 → 17, and related crates
• Remove the op feature flag from alloy-evm and reth-rpc-eth-api dependencies entirely

Key changes

• alloy-op-evm: Add OpTx newtype with trait impls (FromRecoveredTx, FromTxWithEncoded, IntoTxEnv, TransactionEnvMut) previously behind alloy-evm's op feature. Default OpEvm/OpEvmFactory Tx param to OpTx. Adapt to alloy-evm 0.30 API changes (TxResult::into_result, BlockExecutorFactory::create_executor signature, BlockEnv::slot_num via EIP-7843 tracked in Support EIP-7843 slot_num in BlockEnv for OP Stack #19853, removal of set_state_clear_flag).
• op-alloy-rpc-types: Add reth feature with reth-rpc-traits impls (FromConsensusTx, TryIntoSimTx, SignableTxRequest) for OP types.
• op-reth: Add OpTxEnvConverter to handle OpTransactionRequest → OpTx conversion via TxEnvConverter trait (bypasses orphan rule). Wire it into OpRpcConvert. Remove op feature from reth-rpc-eth-api.
• Workspace: Reorganize reth deps in Cargo.toml — crates.io-published crates (reth-codecs, reth-primitives-traits, reth-rpc-traits, reth-zstd-compressors) listed separately from git deps. Remove stale [patch.crates-io] entries (only rollup-boost patches remain).

Test plan

• cargo check --workspace passes
• cargo clippy --workspace -- -D warnings passes
• cargo test -p alloy-op-evm — all 24 tests pass
• cargo test --workspace --doc — all doctests pass
• cargo +nightly fmt --check passes
• RUSTDOCFLAGS="--cfg docsrs -D warnings" cargo +nightly doc --workspace --all-features --no-deps passes
• zepter passes
• CI: memory-all-* failures are pre-existing acceptance test infra issues

🤖 Generated with Claude Code

Important note

Bump MSRV to 1.94

[wiz-inc-a178a98b5d]

Wiz Scan Summary

Scanner	Findings
Vulnerabilities	-
Sensitive Data	-
Secrets	-
IaC Misconfigurations	1  1  1  1
SAST Findings	1
Software Management Findings	-
Total	1  2  1  1

View scan details in Wiz

To detect these findings earlier in the dev lifecycle, try using Wiz Code VS Code Extension.

[codecov]

Codecov Report

❌ Patch coverage is 53.22196% with 392 lines in your changes missing coverage. Please review.
✅ Project coverage is 76.0%. Comparing base (3b2194d) to head (c52d477).
⚠️ Report is 16 commits behind head on develop.

Files with missing lines	Patch %	Lines
rust/alloy-op-evm/src/tx.rs	38.1%	81 Missing ⚠️
rust/op-reth/crates/payload/src/payload.rs	49.6%	81 Missing ⚠️
rust/op-reth/crates/node/src/node.rs	10.4%	43 Missing ⚠️
rust/op-alloy/crates/consensus/src/reth_codec.rs	82.1%	36 Missing ⚠️
rust/op-alloy/crates/consensus/src/reth_core.rs	21.4%	33 Missing ⚠️
rust/op-alloy/crates/rpc-types/src/reth_compat.rs	0.0%	25 Missing ⚠️
rust/op-reth/crates/cli/src/app.rs	0.0%	13 Missing ⚠️
rust/op-reth/crates/evm/src/tx.rs	0.0%	12 Missing ⚠️
rust/op-reth/crates/rpc/src/debug.rs	0.0%	10 Missing ⚠️
rust/op-reth/crates/payload/src/traits.rs	46.1%	7 Missing ⚠️
... and 24 more

Additional details and impacted files

@@             Coverage Diff             @@
##           develop   #19854      +/-   ##
===========================================
+ Coverage     75.3%    76.0%    +0.7%     
===========================================
  Files          195      688     +493     
  Lines        11343    73263   +61920     
===========================================
+ Hits          8544    55720   +47176     
- Misses        2655    17399   +14744     
  Partials       144      144              

Flag	Coverage Δ
cannon-go-tests-64	66.4% <ø> (ø)
contracts-bedrock-tests	80.7% <ø> (+0.5%)	⬆️
unit	76.1% <53.2%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
rust/alloy-op-evm/src/env.rs	84.0% <ø> (ø)
rust/alloy-op-evm/src/lib.rs	89.3% <100.0%> (ø)
.../bin/client/src/fpvm_evm/precompiles/test_utils.rs	87.3% <100.0%> (ø)
...ust/kona/crates/proof/executor/src/builder/core.rs	88.7% <100.0%> (ø)
rust/kona/crates/proof/executor/src/db/mod.rs	97.0% <ø> (ø)
rust/op-reth/crates/evm/src/lib.rs	99.7% <ø> (ø)
rust/op-reth/crates/node/src/engine.rs	76.6% <100.0%> (ø)
rust/op-reth/crates/node/src/rpc.rs	100.0% <100.0%> (ø)
rust/op-reth/crates/node/src/utils.rs	34.0% <100.0%> (ø)
rust/op-reth/crates/primitives/src/receipt.rs	93.1% <ø> (ø)
... and 39 more

... and 447 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[theochap]

DON'T IGNORE DOC COMMENTS

[sebastianst]

still needs to be fixed? :D

[theochap]

Fix: proof history initialization with packed trie keys

The integration tests (op-reth-e2e-sysgo-tests, rust-e2e-simple-kona) were failing with:

Error: write operation CursorAppendDup failed for key "000...0001" in table AccountTrieHistory:
the given key value is mismatched to the current cursor position (-30418)

Root cause

Reth commit 80bf5532a (perf(trie): pack StoredNibblesSubKey from 65→33 bytes, generic cursor factory (#22158)) introduced packed nibble encoding for trie keys. Previously, StoredNibbles stored 1 nibble per byte (65 bytes). The packed format (PackedStoredNibbles) stores 2 nibbles per byte (33 bytes), a 50% size reduction that preserves memcmp sort order.

Key types introduced:

• PackedStoredNibbles / PackedStoredNibblesSubKey (33-byte fixed layout)
• PackedAccountsTrie / PackedStoragesTrie — table views sharing the same underlying MDBX tables as AccountsTrie / StoragesTrie
• PackedKeyAdapter vs LegacyKeyAdapter for runtime dispatch via a with_adapter! macro
• StorageSettings { storage_v2: bool } metadata flag to select encoding at runtime

Critically, StorageSettings::base() now returns v2() (storage_v2: true), meaning all new databases use packed encoding by default. The init_genesis function calls StorageSettings::base(), so genesis trie entries are written with PackedAccountsTrie (33-byte packed keys).

What broke

The proof history initialization code (op-reth/crates/trie/src/initialize.rs) was reading from tables::AccountsTrie (unpacked 65-byte key view), but the underlying MDBX table contained packed 33-byte keys. Since both table views share the same MDBX table name, the cursor returned raw packed bytes which StoredNibbles::Decode interpreted as unpacked nibbles — producing garbage nibble values. When these garbage nibbles were sorted and written to AccountTrieHistory via append_dup, the misordered keys caused the MDBX MDB_KEYEXIST error.

Fix

Updated AccountsTrieInit to read from tables::PackedAccountsTrie instead of tables::AccountsTrie, so the cursor correctly decodes packed keys into PackedStoredNibbles. The Nibbles values extracted from PackedStoredNibbles are correct, and the downstream store_account_branches sorts and writes them properly.

Files changed:

• op-reth/crates/trie/src/initialize.rs — switched AccountsTrieInit to use PackedAccountsTrie + PackedStoredNibbles, updated initialize_accounts_trie to read from the packed table, updated unit tests accordingly

[sebastianst]

first 73 or 104 files reviewed.

[sebastianst]

why is it safe to remove these assertions from the test?

[sebastianst]

still needs to be fixed? :D

[sebastianst]

OK this lgtm besides the comments from the first review. However, I couldn't review every line in detail, it's too much. I skimmed most bits that looked like mechanical plumbing.