The Ethereum JSON-RPC Interface

How it was measured

Tiers are measured by calling the methods, not by counting published specs. A JSON-RPC provider exposes one endpoint and declares no paths, so there is nothing to count; the endpoints are public, so there is something to call.

The core tier

What a provider has to implement before a compatibility claim means anything. Every placement is measured, and the evidence for each sits in the tier profile.

eth_blockNumbereth_chainIdeth_estimateGaseth_gasPriceeth_getBlockByNumbereth_getBlockTransactionCountByNumbereth_getTransactionCountnet_versioneth_calleth_feeHistoryeth_getBalanceeth_getCode

Adopters

Every entry in the registry carries the URL it was read from and the date it was read. A claim is never promoted to a verdict.

Providers that reach a tier

8 of the 40 recorded adopters demonstrably reach the core tier or better.

BerachainInfinitySwapManta NetworkTenderlyZircuitZoraLineaMantle Network

Artifacts

Everything this standard publishes. All of it is generated from the profile, so a re-measurement moves every artifact together.

Source