Blockchain
Nobody ratified the Ethereum JSON-RPC interface as a standard for every other chain. It became one because every EVM chain and every node provider implemented it, and a client written for one now points at hundreds by changing a URL. This profile measures what that actually gets you — by calling the methods.
| Cohort | reimplementation — independent nodes and gateways serving one method set |
|---|---|
| Status | Published — 78 methods graded from 42 live endpoint probes, 40 adopters recorded |
| Repository | https://github.com/api-commons/blockchain |
| Profiles | 1 in this domain |
The Ethereum JSON-RPC Interface
The eth_* method set as public endpoints actually serve it. 22 methods are core here against 2 for the OpenAI interface — the EVM ecosystem is far more uniformly implemented than the model layer.
| Identifier | eth-jsonrpc |
|---|---|
| Originator | Ethereum |
| Source of truth |
ethereum/execution-apis
CC0-1.0
Pinned at 5aebdfdd45cadeb723be4bd45b4611b71c8b1c85
OpenRPC 1.2.4, release v1.0.0-beta.7 — 78 methods across eth, engine, debug, txpool and net. Public domain, the cleanest source of any standard in this programme. |
| How it was measured | Not read — called. A JSON-RPC provider exposes one endpoint and a method name in the body, so there are no paths to count; of 86 providers claiming EVM compatibility, some publish a path per method, some a single slash, most nothing at all. The endpoints are public and unauthenticated by design, so 42 were probed read-only and 21 produced usable results. Only JSON-RPC error -32601 proves a method absent: any other error code means the method exists and rejected the call. |
| Tier | What it covers |
|---|---|
| Core 22 operations |
Served by a majority of probed endpoints. eth_blockNumber, eth_chainId, eth_estimateGas, eth_gasPrice, eth_getBlockByNumber and net_version all sit at 95.2%. The median endpoint serves 20 of the 22 and eight serve every one — the core is what a majority serve method by method, which is not the same as any one endpoint serving all of it. |
| Extended 6 operations |
eth_coinbase (47.6%), eth_config and txpool_status (28.6%), the debug namespace, and eth_capabilities at 9.5%. |
| Vendor 50 operations |
Under 5%, or not probed. This includes all 25 engine_* methods — the consensus-layer API, spoken between a node's execution and consensus clients over an authenticated port. No public endpoint served any of them, and that is the correct result rather than a gap. |
40 implementations recorded · as of 2026-09-13
| Evidence | Count | Meaning |
|---|---|---|
tested | 21 | The methods were called against a live public endpoint. This is the only profile in the programme where `tested` is the ordinary grade rather than the aspirational one, because the endpoints cost nothing to reach. |
prose | 19 | Could not be probed — unreachable, refused at the edge, or failed the negative control. No tier is recorded for any of them: an endpoint we could not read is not an endpoint that failed. |
declared | 0 | Nobody in this cohort publishes an OpenRPC document we could lint. The ruleset exists for when they do. |
The full adopter registry · the adopter matrix — every entry carries the URL it was read from and the date it was read.
Artifacts
-
OpenRPC
— OpenRPC
The artifact of record — the profile in the protocol's own format, x-tier on every method. -
OpenAPI
— OpenAPI
A labelled convenience: one path, method as a const in the body. A path per method would read more naturally and would describe an API nobody serves. -
Profile
— Profile
All 78 methods with their tier and the probe evidence behind it. -
Spectral Ruleset
— SpectralRules
Generated from the profile — 22 core-method rules plus three hygiene rules. -
Arazzo
— Arazzo
eth_chainId, then eth_blockNumber, then the block at that height. -
MCP Tools
— MCP
MCP tool definitions for all 22 core methods.
Licensing
The profile is independently authored from a public-domain source. ethereum/execution-apis is CC0-1.0, which carries no obligations beyond honesty about provenance. API Commons artifacts are CC BY-NC-SA 4.0 and code is Apache-2.0. Ethereum JSON-RPC is a community specification; nothing here implies endorsement by the Ethereum Foundation or by any provider named in the registry.
Tags
BlockchainEthereumWeb3Cryptocurrency
Further reading
- The adopters building block — The schema behind the registry. Probing these endpoints added `inconclusive` to it — an endpoint that fails its negative control misleads in both directions.
- The adopter matrix — Method by endpoint, with the core-coverage spread.