Repository navigation
study: add Base, Arbitrum, tip blocks and log ranges - #17
Merged
Merged
Conversation
The study only asked Ethereum mainnet for a balance, a USDC call and the head, which is where providers almost never differ. It now also covers: - Base and Arbitrum, four public endpoints each, verified only against endpoints on the same chain. - eth_getBlockByNumber at the tip, where reorgs and lagging nodes show. - eth_getLogs over the last 10 blocks of USDC transfers (every 4th tick), where providers truncate. Ranges stay short and recent because free tiers cap them and treat older ranges as archive requests. The report groups disagreements by chain, measures head lag in seconds so chains with different block times compare, and stops counting a null answer (a node not yet at that height) as a differing one. A two-minute smoke run already found one real difference: the official Arbitrum RPC returns blockTimestamp "0x0" on every log, where the other three providers return the block's time. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
macjayz
enabled auto-merge
November 1, 2026 10:26
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
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.
Stacked on #16. The diff below only shows this change.
The study used to ask Ethereum mainnet for a balance, one USDC call and the head, which is where providers almost never disagree. It now also covers the harder cases:
eth_getBlockByNumberat the tip, where reorgs and lagging nodes show.eth_getLogsover the last 10 blocks of USDC transfers, every 4th tick, where providers truncate. Ranges stay short and recent because free tiers cap them (BlastAPI: 10 blocks) and treat older ranges as archive requests.Report changes:
nullanswer (a node not yet at that height) is no longer counted as a differing answer. Before this fix, it turned the official Arbitrum node's tip lag into a fake 27% block disagreement.Found already: a two-minute smoke run caught the official Arbitrum RPC (
arb1.arbitrum.io/rpc) returningblockTimestamp: "0x0"on every log, while dRPC, BlastAPI and publicnode return the block's real time. Confirmed with directcurls against each endpoint.Tested: two smoke runs of the collector (13 endpoints) against a local stack, plus the report against both. Linted and typechecked.
🤖 Generated with Claude Code