Unable to Convert Existing Sepolia Full Node to Distance-Pruned Node (UnexpectedStaticFileBlockNumber)

[zahidmahmood-224]

I'm trying to convert an existing Sepolia full node (restored from an EthPandaOps snapshot) into a distance-pruned node, but Reth crashes as soon as pruning is enabled.

Environment

• Network: Sepolia
• Snapshot provider: EthPandaOps
• Snapshot block: 10,840,000
• Snapshot metadata:
  --full --prune.bodies.pre-merge --prune.receipts.before=1450409
• Current chain head: ~11.27M blocks

Tested versions

• ✅ Reth v2.3.0
• ✅ Reth v2.2.0 (same result)

Desired pruning config
--prune.transaction-lookup.distance 120000 --prune.receipts.distance 120000 --prune.account-history.distance 120000 --prune.storage-history.distance 120000 --prune.bodies.distance 120000

The node starts normally, syncs, and begins processing new blocks, but after the first few blocks it crashes with:
`ERROR engine::persistence: Persistence service failed
ProviderError(
UnexpectedStaticFileBlockNumber(
TransactionSenders,
11269053,
11000000
)
)

ERROR engine::tree: Polling persistence failed
ERROR engine::tree: Fatal error
ERROR reth::cli: Fatal error in consensus engine`

If I remove the pruning flags and use the original snapshot configuration, the node works perfectly.

Question:
Is in-place conversion from an existing full snapshot database to a distance-pruned database supported?