search

ethereum-optimism / op-geth

GNU Lesser General Public License v3.0
290 stars 757 forks source link

op-geth cannot be safely pruned on Optimism mainnet #193

Open yorickdowne opened 11 months ago

yorickdowne commented 11 months ago

System information

Geth version:

Version: 0.1.0-unstable
Git Commit: ed8e9f54ed0a5069e77ea34895ff12a9ac4ca17f
Upstream Version: 1.13.4-stable

CL client & version: op-node version v0.0.0-74ff044a-1699318761

Behaviour

Using snapshot prune-state with op-geth gets through all three steps - Iterating, Pruning, Compacting - and then after op-geth starts again, it complains that its DB is corrupted.

If pruning is not supported with op-geth, I recommend disabling the function altogether.

Steps to reproduce the behaviour

Sync an Optimism node on mainnet (have not tested this on Goerli but shall if desired), stop op-geth, and run a prune.

Any network other than Optimism mainnet/goerli would be on PBSS, and so this issue would not ever show.