gas bench: use dRPC for Avalanche verify (api.avax lags primary) - #1495
Merged
Conversation
…inality lag caused verify_fetch_err on every block)
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.
Primary avalanche RPC (
avalanche-c-chain-rpc.publicnode.com) is one block ahead ofapi.avax.network, so every verify fetch throws "cannot query unfinalized data" and inflates the verify_fetch_err counter. dRPC keeps parity with the primary. Ethereum and Polygon verify remained clean (0 disagreements) — this is only for Avalanche.