Enhancement of Cache Management in Staged Stream Sync #4956
Conversation
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
mur-me
approved these changes
Oct 14, 2025
GheisMohammadi
force-pushed
the
fix/testnet_instability
branch
from
9963b1c to
38d4fb7
Compare
Frozen
approved these changes
Oct 15, 2025
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.
This PR addresses testnet instability issues by implementing robust block cache management and validation mechanisms in the staged stream synchronization process. The changes focus on preventing data corruption and ensuring reliable block synchronization across the network. It removes unused cache functionality in the stage block hashes component. This simplification helps reduce the complexity of the caching system and makes the code more maintainable. It introduces comprehensive validation for block hashes stored in the cache before they are used during synchronization. The PR implements automatic cleanup of block caches when block data is detected as corrupted or not properly saved. This self-healing mechanism ensures that when data integrity issues are detected, the system can recover by clearing the problematic cache entries and allowing fresh data to be fetched. This prevents the accumulation of bad data that could cause persistent synchronization issues.