DEVELOPERS / 01

Connect with
context.

JSON-RPC compatibility varies by client, method, and transport. Inspect the source-backed matrix before relying on an API.

Swipe the table to compare all four clients →

Present in source Partial / limited Missing / not measured

xOne family source comparison, 14 November 2026
CAPABILITY	xOneRSRUST	xOneCC++	xOnePyPYTHON	xOneTSTYPESCRIPT
eth_call	Runtime missingAdapter refuses callsSource	PresentSource	PresentSource	PresentSource
Gas estimation	Runtime missingSource	MissingReturns an errorSource	PresentSource	PresentSource
Debug tracing	PartialHandlers; runtime adapter missingSource	MissingSource	MissingSource	MissingSource
Admin peers	PresentSource	MissingSource	MissingSource	MissingSource
IPC transport	PresentHardening work remainsSource	MissingAccepted flags are inertSource	MissingAccepted flags are inertSource	MissingAccepted flags are inertSource
Log subscriptions	PresentSource	PartialSubscription accepts; no eventsSource	PresentSource	PresentSource
Fee history rewards	PartialSemantics tracked in #256Source	PartialRewards are zero-filledSource	PartialRewards are zero-filledSource	PresentSource

Present = implemented in inspected source. Partial = known limitations or incomplete runtime wiring. These are source findings, not live certification.

Client implementation comparison. Source review dated 14 November 2026.
CLIENT	LANGUAGE	NETWORK / ROLE	PERFORMANCE / OPERATIONS	EXPLORE
xOne familyFour development implementations	Rust · C++ · Python · TS	XDC / XDPoS	Independent implementations & conformance	Source
XDPoSChainXDC reference	Go	XDC / XDPoS	XDC protocol & node operation	Source
Gethgo-ethereum	Go	Ethereum execution	Snap state synchronization	Source
Rethparadigmxyz/reth	Rust	Ethereum execution	Archive, full, minimal & custom pruning	Source
Erigonerigontech/erigon	Go	Ethereum execution	History profiles & snapshot retirement	Source
NethermindXDC plugin present in source	C#	Ethereum · XDC plugin	Configurable state pruning	Source
Besubesu-eth/besu	Java	Ethereum & private networks	Performance, JVM & operations guides	Source
ethrexlambdaclass/ethrex	Rust	Ethereum execution	Snap synchronization design	Source

Historical source snapshot. Source links point to commit 5af188d; text was reviewed 14 November 2026 and may differ from newer client builds.

01 /

Read-only requests

The example targets a local HTTP endpoint at port 8545. Replace the URL if your node uses another port. No requests are sent by this page.

curl http://127.0.0.1:8545 \
  -H "Content-Type: application/json" \
  --data '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}'

# Repeat with eth_blockNumber or eth_syncing to inspect progress.

02 /

Method presence is not runtime support

A namespace flag or handler declaration does not prove a working end-to-end method. The source review distinguishes implemented, partial, and missing behavior, including transport and subscription limits.

Method-level reference Rust RPC method documentation Full client comparison Engineering audit

03 /

Plan for bounded access

Enable only the namespaces your application needs. Keep administrative, debugging, signing, and public application traffic separate. Review transport binding, authorization, timeouts, and response limits in the selected client’s documentation.

Security and reporting

FOLLOW THE SOURCE

Reviewed 14 November 2026. Repository guides hold the current implementation details.

RPC reference CLI flags

KEEP THE CURIOSITY GOING

Another way in.

The client family Developer handbook Field notes

Edit this page on GitHub opens the data definition (data/site-pages.js). GitHub may ask you to sign in. Report a correction opens a prefilled GitHub issue for this page.