Remove Blast API as an outdated node provider #587
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
Add specialized guide for Base node sync issues based on community reports (base#127, base#251, base#369, base#413, base#419, base#433). Includes: - 4 sync scenarios with Check/Action solutions - Hardware anti-patterns (RAID-5, NAS, SATA warnings) - Reth performance optimization - Monitoring commands and quick reference
Collaborator
🟡 Heimdall Review Status
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Blast API is officially shutting down access on October 31st (today is October 28th). Their official website redirects users to Alchemy and states: "Blast API access ends after Oct 31. Switch to Alchemy for blockchain data"