[OP Stack Deployment] Uncomplete archive node snapshot #938
Unanswered
free-cornet
asked this question in
Deploying the OP Stack
Replies: 1 comment
-
|
Is there any developer from Optimism responsible for providing the op-reth or op-geth archive snapshots hosted on datadir.optimism.io who could confirm whether those archive snapshots are missing data from the post-Bedrock upgrade period up to the present? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Did you check the documentation?
Did you check for duplicate questions?
Issue Description
I'm desperately trying to deploy a local archive node for the optimism mainnet. I've tried with both op-geth and op-reth. I've followed the provided documentation to "Run an archive node" https://docs.optimism.io/node-operators/guides/management/archive-node.
I've started my nodes from the official archive snapshot provided by Optimism (via datadir.optimism.io), using mainnet-2025-07-17.tar.zst and mainnet-reth-archive-2026-05-12.tar.zst for op-geth and op-reth, respectively.
My issue lies in the fact that those archive snapshots seem to have missing/pruned data, and that those data won't be retrieved through the P2P network.
One example of this is trying to retrieve the execution trace of some transaction post-bedrock (I don't need data from before the bedrock update). This command:
results in this output:
Am I missing something? Is there a way to force data retrieval for missing/pruned data?
Logs
No response
Additional Information
No response
Feedback
Improving the documentation on how to run an optimism archive node and what could be expected would be great.
The same goes for the documentation about the archive snapshots and what is part of it, how to use them, and what the naming convention is.
Beta Was this translation helpful? Give feedback.
All reactions