Repository navigation
six chain RPC benches that nobody answers - #2785
Merged
Merged
Conversation
An audit of all 161 chain RPC benches found seven with no provider producing a number. Each declared endpoint was re-tested by hand, with the right protocol per chain rather than eth_blockNumber everywhere, which is what separated the dead from the merely non-EVM. Six are retired: quicksilver 0 of 3 endpoints alive, last sample 29 days old thundercore 0 of 3 (two answer 503), 24 days canto 0 of 1 (connection times out), 24 days neon 0 of 3, 8 days plume 0 of 1 (drpc answers 400), probe fresh zetachain 1 endpoint alive, 0.37 % success, probe fresh The last two are the pair worth reading twice. Their probes run and their data is current, and what the data says is that nobody answers. zetachain's single endpoint is Thirdweb, which serves browsers and refuses our probe hosts on every chain we measure it (0.3 % to 1.5 % across 29, see #2779). The seventh, starknet-rpc, is NOT retired. Its probe has produced unbroken data for at least seven days, OnFinality clears the 50 % floor at 50.69 % with a 339 ms p50, and every query the spec declares resolves against Prometheus right now. The published blob is 585 hours old regardless, so the bench is a publication bug and not a dead chain. Removing it would have destroyed working measurement. Specs deleted, slugs added to REMOVED_BENCH_SLUGS so indexed URLs answer 410 Gone rather than 404, matcher kept in sync (its test caught the first attempt, which had the wrong indentation and inserted nothing). The six chains leave the harness too, so three probe regions stop spending calls on endpoints that time out. Five leave the chain registry with their bench, which removes an empty /chains page: each linked the RPC bench and nothing else, and all six were already out of the sitemap. plume stays in the registry because chain-bridged-tvl and chain-fees-revenue measure it. The harness edit took three attempts. A regex over the Go composite literal left an orphan brace twice; `go build` caught both. The version here cuts on exact line boundaries and passes build and vet.
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.
Cherry-pick from dev (#2784). This commit only.
An audit of all 161 chain RPC benches found seven with no provider producing a number. Each declared endpoint was re-tested by hand with the right protocol per chain, which is what separated the dead from the merely non-EVM.
Retired:
quicksilver-rpc(0/3 endpoints, 29 days),thundercore-rpc(0/3, two answer 503),canto-rpc(0/1, times out),neon-rpc(0/3),plume-rpc(0/1, drpc answers 400) andzetachain-rpc(1 endpoint, 0.37 % success). The last two have fresh probes and current data; what the data says is that nobody answers.starknet-rpcis deliberately kept. Its probe has produced unbroken data for seven days, OnFinality clears the 50 % floor at 50.69 % with a 339 ms p50, and every spec query resolves against Prometheus now. The 585-hour-old blob is a publication bug, not a dead chain.Slugs answer 410 Gone, the matcher is in sync, the six leave the harness so three probe regions stop calling endpoints that time out, and five leave the chain registry.
plumestays there becausechain-bridged-tvlandchain-fees-revenuemeasure it.Verified after the pick: 235 specs valid, 444 tests, harness builds and vets clean.