Skip to content

Measurements

Which RPC methods each provider answers

Which methods each provider actually answers, established by calling them rather than by reading a documentation page. Support varies far more than provider marketing suggests, and a fast endpoint that only answers two methods is not a fast endpoint.

Choosing a provider?Which provider leads overallMethod support is one input. The ranking weighs it alongside latency, uptime and correctness.

24h window · 14 methods × 5 providers

In this matrix:Blast APIBNB ChainNodeReal1RPCPublicNode

How to read this matrix

  • Supported— Answered correctly and consistently
  • Degraded— Answered, but with failures in the window
  • Failing— Called and failed most of the time
  • Unsupported— Method rejected by the endpoint
  • Rate limited— Throttled too often to judge
  • Not measured— No samples in this window

14 methods

Take it awayCSV— method support on BSCJSON— method support on BSCone row per method and provider, not the matrix

What each method does

Written against the primary specifications — the Ethereum JSON-RPC docs and the Solana RPC docs — rather than from memory. Each page carries the parameters, the caveats that actually bite, and a runnable example against a keyless endpoint.