rpc hub (D): archive depth column - #1552
Merged
Merged
Conversation
… into bench blob, exposes bestArchiveDepthBlocks in snapshot, displays as sortable column
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.
Ship D from the /rpc audit. Data was already collected by the harness (rpc_archive_depth_supported metric, 2415 series) but never made it to the hub.
Pipeline
archiveDepth?: { supportedBlocks: number[] }-rpcspecs, one extra Prom querymax by(provider, depth)(rpc_archive_depth_supported{chain=X} == 1)groups supported depths per provider, attaches to result rows. Failure is silent (nice-to-have)archiveDepth, RpcHubChain gainsbestArchiveDepthBlocks(max of leader's supported set), mapper populates bothRate limits
Zero new RPC probes. Harness already collects archive depth every 1h/(chain,provider,region,depth). Extra load = 1 Prom query per -rpc bench per materialization cycle (~41 queries/cycle, cheap).
What users will see
Providers like Thirdweb (pruned per our live probe) render '300' in gray; chain-official + full-archive gateways render '5M+' in normal weight. Instant signal for indexer / subgraph builders who need historical state.