feat: add --skip-merkle flag to correct-last-epoch command #271
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.
Summary
--skip-merkle
flag to thecorrect-last-epoch
command that skips merkle root computationMotivation
This feature is useful when multiple networks need correction. Previously, if we tried to fetch the last reported block for a network and it was a non-existent block, the script would fail. With
--skip-merkle
, we can bypass fetching blocks from other chains entirely, avoiding these failures.Changes
--skip-merkle
CLI flag toCorrectLastEpoch
command--skip-merkle
is set and block number is provided: skip all RPC initialization--skip-merkle
is set but block number needs auto-detection: only initialize target chain RPC--skip-merkle
is not set: initialize all RPCs (existing behavior)Test plan
--skip-merkle
flag--skip-merkle
and explicit block number--skip-merkle
and auto-detected block number🤖 Generated with Claude Code