docs: add troubleshooting section for MissingL1InfoDeposit error with pruned snapshots#1126
Open
Kewe63 wants to merge 4 commits into
Open
docs: add troubleshooting section for MissingL1InfoDeposit error with pruned snapshots#1126Kewe63 wants to merge 4 commits into
Kewe63 wants to merge 4 commits into
Conversation
added 4 commits
June 6, 2026 14:40
…ETH_MAX_OUTBOUND_PEERS
… pruned snapshots
Collaborator
🟡 Heimdall Review Status
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds a new troubleshooting subsection to the README covering the
EngineReset(SyncStart(FromBlock(MissingL1InfoDeposit(...))))error that users may encounter when syncing a Base node from a pruned snapshot that lacks sufficient historical data for consensus client initialization.Problem
Users syncing from an older pruned snapshot may experience a consensus client crash with a
MissingL1InfoDepositerror for a specific block hash. Pruned snapshots discard historic state, and if the snapshot predates the early blocks required for deposit contract verification, the consensus client cannot complete initialization.Solution
The added subsection explains the root cause and provides clear, actionable remediation steps:
/databy default).An example command block for clearing data and restarting the node is included.
Test Results
catand visual inspection).Risk
None. This is a documentation addition only and has no effect on the node software, build process, or runtime behavior.