sync: provider fixes for boba/zircuit/sanko/corn/comdex benches - #1774
Merged
Conversation
…ex benches boba: use mainnet.boba.network + boba-eth.drpc.org (remove BlastAPI alias, ankr 403, replica DNS fail) zircuit: use mainnet.zircuit.com only (drpc returns 400, blastapi DNS fails from Railway) sanko: use thirdweb 1996 gateway (official DNS fails, drpc 404) corn: use thirdweb 21000000 gateway (official DNS fails, drpc 404) comdex: use stavr (comdex.rpc.m.stavr.tech) as sole provider; polkachu DNS fails, publicnode 403, lavenderfive 503 from Railway
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
1 participant
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.
Sync main → dev so the materialize-worker Docker build picks up the updated bench YAMLs.
Changes: