rpc: merkle delist corrected (method gap, not IP block) - #1027
Merged
Conversation
…2601), revert proxy plumbing (wrong diagnosis)
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.
Correction of #1026: merkle's 100% error rate was NOT a datacenter-IP block. Its gateway returns -32601 Method not found for eth_getBlockByNumber from ANY IP; it only serves eth_blockNumber/eth_chainId/eth_call etc. The failures started when the cluster standardized on the anti-cache probe (full latest header + rotating id).
Falling back to eth_blockNumber just for merkle would reintroduce the cacheable-probe hole the methodology exists to close, so merkle is delisted with the accurate reason in the page copy. ViaProxy plumbing reverted (unused).