op-reth storage access is broken due to missing Deposit TxType

[cakevm]

Describe the bug

Starting a op-reth node results in:

2025-02-11T13:58:08.024714Z  INFO Verifying storage consistency.
thread 'main' panicked at crates/storage/codecs/src/alloy/transaction/txtype.rs:44:30:
Unsupported TxType identifier: 126

This issue is related to #14220.

Cause is PR #13830

In crates/primitives/src/transaction/tx_type.rsthe TxType was removed that contained:

pub enum TxType {
    ...
    /// Optimism Deposit transaction.
    #[cfg(feature = "optimism")]
    #[display("deposit (126)")] <-- missing in alloy_consensus
    Deposit = 126_isize,
    ...

This is now

pub use alloy_consensus::TxType; <-- missing op types

As a result in crates/storage/db-api/src/models/mod.rs the TxType is now from alloy_consensus and is missing the optimism types:

impl_compression_for_compact!(
    ...
    TxType
    ...
);

Steps to reproduce

Checkout 0f5d60, build op-reth and start it with existing db.

Node logs

Platform(s)

No response

Container Type

Not running in a container

What version/commit are you on?

0f5d60

What database version are you on?

Current database version: 2
Local database version: 2

Which chain / network are you on?

base

What type of node are you running?

Archive (default)

What prune config do you use, if any?

No response

If you've built Reth from source, provide the full command you used

make op-build

Code of Conduct

• I agree to follow the Code of Conduct

[BowTiedDevil]

I've been watching this one too — the latest tagged image (bae79ec) runs as expected via container, the TxType 126 panic is resolved.

[emhane]

op-reth main isn't working since #14209

advice running latest release if that is an option

[emhane]

ah sorry, this is only if you're also testing latest hardfork, re-opening

[cakevm]

Thank you @BowTiedDevil, I tried with the latest commit version d727701 and it is now working as expected.