op-reth currently does not support deep historical proofs. By enabling this Execution Extension (ExEx), the node initializes a separate storage database specifically for historical trie nodes. This allows the node to generate and serve historical proofs efficiently, which is critical for applications requiring historical state access, such as fault proof systems.
For a complete setup guide, see the tutorial on Running op-reth with Historical Proofs.
This fork inherits all standard op-reth configuration options. See the op-reth configuration reference.
Proof History
Options for configuring the proof history ExEx.proofs-history
If true, initialize external-proofs exex to save and serve trie nodes to provide proofs faster.- Syntax
--proofs-historyproofs-history.storage-path
The path to the storage DB for proofs history.- Syntax
--proofs-history.storage-path <PROOFS_HISTORY_STORAGE_PATH>proofs-history.window
The window to span blocks for proofs history. Value is the number of blocks. Default is 1 month of blocks based on 2 seconds block time (30 * 24 * 60 * 60 / 2 = 1,296,000).
- Syntax
- Default
--proofs-history.window <PROOFS_HISTORY_WINDOW>proofs-history.prune-interval
Interval between proof-storage prune runs. Accepts human-friendly durations like “100s”, “5m”, “1h”.- Shorter intervals prune smaller batches more often.
- Longer intervals prune larger batches less often.
- Syntax
- Default
--proofs-history.prune-interval <PROOFS_HISTORY_PRUNE_INTERVAL>proofs-history.verification-interval
Verification interval: perform full block execution every N blocks for data integrity.0: Disabled (Default). Always use fast path with pre-computed data.1: Always verify. Always execute blocks.N: Verify every Nth block (e.g., 100 = every 100 blocks).
- Syntax
- Default
--proofs-history.verification-interval <PROOFS_HISTORY_VERIFICATION_INTERVAL>Management Commands
Theop-reth proofs command allows you to manage the storage of historical proofs.