[Node Operator Question] Pruning issue with archive node using OP-Reth

[free-cornet]

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've tried to deploy a local archive Optimism node, using op-reth and op-node. As explained in the documentation, I've retrieved some snapshots needed to start the archive node post-bedrock update. I've tried with several archives, the last one being mainnet-reth-archive-2026-04-21.tar.zst, coming from this link:
https://datadirs.optimism.io/
mentioned in the Optimism documentation.

My issue is that, while my archive node is synced (confirmed with eth_syncing) and I can retrieve transaction details with eth_getTransactionByHash, I'm unable to retrieve data such as the receipt using eth_getTransactionReceipt, returning

{"jsonrpc":"2.0","id":1,"result":null})

nor the execution trace with the built-in callTracer, resulting in

{"jsonrpc":"2.0","id":1,"error":{"code":-32603,"message":"Revm error: failed to apply 4788 system call failed to apply beacon root contract call at 0x6bfe01c0f2b243dc6d6598d9b5e4c14b954f280f1d20db522f6c447d5338729f: database error: Database error: state at block #124037012 is pruned"}}

letting me think that part of the state has been pruned.
Note that I'm only trying to retrieve such data for the post-bedrock update transaction.

Steps to Reproduce

After building op-reth and op-node for your environment (I'm doing it in a VM), download the snapshot mainnet-reth-archive-2026-04-21.tar.zst available on https://datadirs.optimism.io/ and uncompressed in your datadir.

Then start your op-reth and op-node with the following config:

For op-reth:

op-reth node \
  --chain optimism \
  --datadir /mnt/blockchain/optimism/datadir \
  --http \
  --http.addr "::" \
  --http.port 8548 \
  --http.corsdomain "*" \
  --http.api eth,net,web3,debug,trace \
  --ws \
  --ws.addr "::" \
  --ws.port 8547 \
  --ws.origins "*" \
  --ws.api eth,net,web3,debug,trace \
  --ipcpath ///mnt/blockchain/optimism/optimism.ipc \
  --authrpc.addr "::" \
  --authrpc.port 8552 \
  --authrpc.jwtsecret /mnt/blockchain/optimism/jwt.txt \
  --port 30305 \
  --rollup.sequencer-http https://mainnet-sequencer.optimism.io/ \
  --discovery.v5.addr.ipv6 :: \
  --discovery.v5.port.ipv6 30303 \
  -vvv

For op-node (connected through ipv6 to my local Ethereum node):

op-node \
  --l1="http://[l1_node_ipv6]:8545" \
  --l1.rpckind=erigon \
  --l1.beacon="http://[l1_node_ipv6]:3500" \
  --l2=http://localhost:8552 \
  --l2.jwt-secret=/mnt/blockchain/optimism/jwt.txt \
  --network=op-mainnet \
  --syncmode=execution-layer \
  --l2.enginekind=reth \
  --l1.trustrpc

Note that for the L1 Ethereum node, I'm using my local node deployed in another VM using Erigon and Prysm.

Which component is affected?

• op-geth
• op-node
• Other

Expected vs. Actual Behavior

Expected

For this command:

curl -X POST http://localhost:8548   -H "Content-Type: application/json"   --data '{
    "jsonrpc":"2.0",
    "method":"eth_getTransactionReceipt",
    "params":["0x67362a6180488e394e2ec27e399b479cef5d030b0c044d35d61b40227eb27acf"],
    "id":1                                                                 
  }'

I'm expecting to obtain the transaction receipt.

And for this one:

curl -X POST http://localhost:8548   -H "Content-Type: application/json"   --data '{
    "jsonrpc":"2.0",
    "method":"debug_traceTransaction",
    "params":[                                                                      
      "0x67362a6180488e394e2ec27e399b479cef5d030b0c044d35d61b40227eb27acf",
      {"tracer": "callTracer"}
    ],
    "id":1
  }'

I'm expecting to receive the trace.

Actual

For the receipt, I received:

{"jsonrpc":"2.0","id":1,"result":null}

And for the trace:

{"jsonrpc":"2.0","id":1,"error":{"code":-32603,"message":"Revm error: failed to apply 4788 system call failed to apply beacon root contract call at 0x6bfe01c0f2b243dc6d6598d9b5e4c14b954f280f1d20db522f6c447d5338729f: database error: Database error: state at block #124037012 is pruned"}}

Environment Details

The execution environment is inside a VM.

• OS: Ubuntu 24.04.4 LTS (Noble Numbat)

Protocol Information

op-reth:

Reth Version: 1.11.3-dev
Commit SHA: d6324d63e27ef6b7c49cdc9b1977c1b808234c7b
Build Timestamp: 2026-03-27T09:41:35.311678418Z
Build Features: asm_keccak,jemalloc,keccak_cache_global,otlp
Build Profile: release

op-node:

op-node version v1.16.9-2954d9fd-1773856987

Network name: OP Mainnet

chain ID: 10

L1 chain: Ethereum Mainnet

Node Logs

For op-reth (at start):

op-reth[16769]: 2026-04-30T09:26:02.437883Z  INFO Pruner initialized prune_config=PruneConfig { block_interval: 5, segments: PruneModes { sender_recovery: None, transaction_lookup: None, receipts: Some(Distance(10000000000)), account_history: None, storage_history: None, bodies_history: None, receipts_log_filter: ReceiptsLogPruneConfig({}) } }
op-reth[16769]: 2026-04-30T09:26:02.439584Z  INFO Consensus engine initialized
op-reth[16769]: 2026-04-30T09:26:02.453351Z  INFO Engine API handler initialized
op-reth[16769]: 2026-04-30T09:26:02.476427Z  INFO RPC auth server started url=[::]:8552
op-reth[16769]: 2026-04-30T09:26:02.477309Z  INFO RPC IPC server started path=///mnt/blockchain/optimism/optimism.ipc
op-reth[16769]: 2026-04-30T09:26:02.477341Z  INFO RPC HTTP server started url=[::]:8548
op-reth[16769]: 2026-04-30T09:26:02.477351Z  INFO RPC WS server started url=[::]:8547
op-reth[16769]: 2026-04-30T09:26:02.477578Z  INFO Starting consensus engine
op-reth[16769]: 2026-04-30T09:26:02.501225Z  INFO Forkchoice updated head_block_hash=0x90c456eae818615a2d541911eca577ad1d8ca8d34cb080edee015ff8b4fdd556 safe_block_hash=0xe9e29cd5643d932670aa0700ec0bc559206b7f0698ff51ba0a7456768b9cde49 finalized_block_hash=0xe9e29cd5643d932670aa0700ec0bc559206b7f0698ff51ba0a7456768b9cde49
op-reth[16769]: 2026-04-30T09:26:05.440258Z  INFO Status connected_peers=3 latest_block=150971186
op-reth[16769]: 2026-04-30T09:27:20.441211Z  INFO Status connected_peers=6 latest_block=150971186

For op-node (at start):

op-node[17226]: t=2026-04-30T11:30:11+0200 lvl=info msg="registered API" route="" namespace=opp2p
op-node[17226]: t=2026-04-30T11:30:11+0200 lvl=info msg="P2P RPC enabled"
op-node[17226]: t=2026-04-30T11:30:11+0200 lvl=info msg="Starting JSON-RPC server"
op-node[17226]: t=2026-04-30T11:30:11+0200 lvl=info msg="Started RPC server" endpoint=http://[::]:9545
op-node[17226]: t=2026-04-30T11:30:11+0200 lvl=info msg="Started JSON-RPC server" addr=[::]:9545
op-node[17226]: t=2026-04-30T11:30:11+0200 lvl=info msg="metrics disabled"
op-node[17226]: t=2026-04-30T11:30:11+0200 lvl=info msg="Starting execution engine driver"
op-node[17226]: t=2026-04-30T11:30:11+0200 lvl=info msg="Starting driver" sequencerEnabled=false sequencerStopped=false recoverMode=false
op-node[17226]: t=2026-04-30T11:30:11+0200 lvl=info msg="Rollup node started"
op-node[17226]: t=2026-04-30T11:30:11+0200 lvl=info msg="State loop started"
op-node[17226]: t=2026-04-30T11:30:16+0200 lvl=info msg="attempting connection" peer=16Uiu2HAm...
op-node[17226]: t=2026-04-30T11:30:16+0200 lvl=info msg="attempting connection" peer=16Uiu2HAm...
op-node[17226]: t=2026-04-30T11:30:16+0200 lvl=info msg="attempting connection" peer=16Uiu2HAk...
op-node[17226]: t=2026-04-30T11:30:16+0200 lvl=info msg="attempting connection" peer=16Uiu2HAm...
op-node[17226]: t=2026-04-30T11:30:16+0200 lvl=info msg="attempting connection" peer=16Uiu2HAm...
op-node[17226]: t=2026-04-30T11:30:16+0200 lvl=info msg="attempting connection" peer=16Uiu2HAm...
op-node[17226]: t=2026-04-30T11:30:16+0200 lvl=info msg="attempting connection" peer=16Uiu2HAk...
op-node[17226]: t=2026-04-30T11:30:16+0200 lvl=info msg="attempting connection" peer=16Uiu2HAk...
op-node[17226]: t=2026-04-30T11:30:16+0200 lvl=info msg="attempting connection" peer=16Uiu2HAm...
op-node[17226]: t=2026-04-30T11:30:16+0200 lvl=info msg="attempting connection" peer=16Uiu2HAm...
op-node[17226]: t=2026-04-30T11:30:16+0200 lvl=info msg="attempting connection" peer=16Uiu2HAm...
op-node[17226]: t=2026-04-30T11:30:16+0200 lvl=info msg="attempting connection" peer=16Uiu2HAm...
op-node[17226]: t=2026-04-30T11:30:16+0200 lvl=info msg="Inserting unsafe L2 execution payload to drive EL sync" id=0x0b28e4fb9fa...:15097...
op-node[17226]: t=2026-04-30T11:30:16+0200 lvl=info msg="Starting EL sync"
op-node[17226]: t=2026-04-30T11:30:16+0200 lvl=warn msg="Clearing safe head db because EL sync started"
op-node[17226]: t=2026-04-30T11:30:16+0200 lvl=info msg="Current hardfork version detected" forkName=jovian
op-node[17226]: t=2026-04-30T11:30:16+0200 lvl=info msg="Inserted new L2 unsafe block (synchronous)" hash=0x0b28e4fb9fab83e84b06c1ce9ca3b111a7aeb3ad3c76193b89acc0a5afcbb73b number=150971319 newpayload_time=23.345ms fcu2_time=1.888ms total_time=25.239ms mgas=11.496115 mgasps=455.4823543954836
op-node[17226]: t=2026-04-30T11:30:16+0200 lvl=info msg="Sync progress" reason="new chain head block" l2_finalized=0x0000000000000000000000000000000000000000000000000000000000000000:0 l2_safe=0x0000000000000000000000000000000000000000000000000000000000000000:0 l2_pending_safe=0x0000000000000000000000000000000000000000000000000000000000000000:0 l2_unsafe=0x0b28e4fb9fab83e84b06c1ce9ca3b111a7aeb3ad3c76193b89acc0a5afcbb73b:150971319 l2_backup_unsafe=0x0000000000000000000000000000000000000000000000000000000000000000:0 l2_time=1777541415
op-node[17226]: t=2026-04-30T11:30:16+0200 lvl=info msg="attempting connection" peer=16Uiu2HAkue...
op-node[17226]: t=2026-04-30T11:30:16+0200 lvl=info msg="attempting connection" peer=16Uiu2HAkvR...
op-node[17226]: t=2026-04-30T11:30:17+0200 lvl=info msg="Inserting unsafe L2 execution payload to drive EL sync" id=0xb9cd1a278b4e89c0a...:150971...
op-node[17226]: t=2026-04-30T11:30:17+0200 lvl=info msg="Finished EL sync" sync_duration=1.144800425s finalized_block=0xb9cd1a278b4e...:150971...
op-node[17226]: t=2026-04-30T11:30:17+0200 lvl=info msg="Inserted new L2 unsafe block (synchronous)" hash=0xb9cd1a278b4e89c0a897d0f2264dee6aff2e1c89cd022a57f4cf836b9e6b4baa number=150971320 newpayload_time=554.901ms fcu2_time=2.208ms total_time=557.238ms mgas=10.228327 mgasps=18.355375871319048

Troubleshooting Attempts

No response

Additional Information

No response

Feedback

The documentation for the deployment of the op-reth archive node is lacking, and some links are broken or redirected.

[LLLshadow]

hi,i have enccounted the same problem,have you solved it?