[Node Operator Question] Unable to bootstrap op-reth from archive snapshots

[angusscott]

Are you running the most up to date node software?

• Yes

Did you check the documentation?

• Yes

Did you check for duplicate questions?

• Yes

Issue Description

I'm attemptiong to bootstrap a new op-reth archive node with the configuration below. Issue I'm having is the chain will not progress from the point it's downloaded.

the result from eth_syncing is below. The only observation I can make is that the reth.toml configuration includes some prune configuration. I am seeing this behavour with the latest op-reth/2.1.0 and with the older op-reth/1.11.3

[prune.segments.merkle_changesets]
distance = 10064

cessed":null,"stages":[{"name":"AccountHashing","block":"0x8fe86f3"},{"name":"Bodies","block":"0x8fe86f3"},{"name":"Era","block":"0x8fe86f3"},{"name":"Exe
cution","block":"0x8fe86f3"},{"name":"Finish","block":"0x8fe86f3"},{"name":"Headers","block":"0x8fe86f3"},{"name":"IndexAccountHistory","block":"0x8fe86f3
"},{"name":"IndexStorageHistory","block":"0x8fe86f3"},{"name":"MerkleChangeSets","block":"0x8d70230"},{"name":"MerkleExecute","block":"0x8fe86f3"},{"name"
:"MerkleUnwind","block":"0x8fe86f3"},{"name":"Prune","block":"0x8fe86f3"},{"name":"PruneSenderRecovery","block":"0x8fe86f3"},{"name":"SenderRecovery","blo
ck":"0x8fe86f3"},{"name":"StorageHashing","block":"0x8fe86f3"},{"name":"TransactionLookup","block":"0x8fe86f3"}]}}

    --chain optimism \
    --rollup.sequencer-http https://mainnet-sequencer.optimism.io \
    --rollup.discovery.v4 \
    --port 30303 \
    --discovery.port 30303 \
    --nat extip:XXX.XXX.XXX.XXX\
    --http \
    --http.api=admin,eth,web3,net,debug,trace,txpool \
    --http.addr=0.0.0.0 \
    --ws \
    --ws.addr=0.0.0.0 \
    --authrpc.port 8551 \
    --authrpc.jwtsecret=/nodes/optimism/jwt.hex \
    --rpc.max-blocks-per-filter=0 \
    --log.file.directory=/home/logs

Steps to Reproduce

Download reth archive snapshot (I've tried both 2026-04-21 and 2026-01-28), and attempt to start a node.

Which component is affected?

• op-geth
• op-node
• Other

Expected vs. Actual Behavior

Node to begin syncing

Environment Details

Rocky 9
Have used both Quicknode and my own Ethereum/consesnus node (Erigon + Teku)

Protocol Information

op-reth 1.11.3-dev and 2.0.0-dev (2.1.0 op-reth)
op-node 1.16.13

Node Logs

No response

Troubleshooting Attempts

No response

Additional Information

No response

Feedback

There is a lack of documentation about running op-reth. Additionally the snapshots should document which version of op-reth/op-geth were sued to generate them as part of the datadirs site. This would make debugging much simpler by reducing the surface of potential issues