Repository navigation
Add --substreams-tier1-allow-pruned-chain flag - #296
Merged
Merged
Conversation
Contributor
sduchesneau
marked this pull request as ready for review
October 13, 2026 20:53
maoueh
approved these changes
Oct 13, 2026
maoueh
approved these changes
Oct 15, 2026
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.
Adds
--substreams-tier1-allow-pruned-chain, which setsTier1Config.AllowPrunedChainfrom streamingfast/substreams#991. With it, tier1 serves modules (mappers and stores) whose initial block is below--common-first-streamable-block, and their stores resume from snapshots taken before the chain was pruned.Tier2 must run this version before the flag is set on tier1: an older tier2 ignores the setting and refuses the jobs.
go.modpoints at the head of streamingfast/substreams#991; it needs a bump once that PR is merged.