RPC vs REST Cheatsheet — JSON-RPC & REST Across Chains
Different chains expose different transport styles: EVM and Bitcoin Core use JSON-RPC, while TRON and TON use REST. This cheatsheet explains each and how 1st Node unifies them.
JSON-RPC chains (EVM, Bitcoin Core)
EVM chains and Bitcoin Core speak JSON-RPC 2.0: you POST an envelope containing jsonrpc, method, params, and id to a single endpoint, and receive a result or error. The method name (eth_getBalance, getblock) selects the operation, and params carries its arguments. One URL serves every method.
REST chains (TRON, TON)
TRON's HTTP API exposes typed paths such as /wallet/getaccount and /wallet/gettransactionbyid, where the URL path names the operation and the body or query carries arguments. TON's HTTP API similarly uses typed REST paths. Here the endpoint path, not a method field, selects the operation.
How 1st Node exposes both
1st Node serves JSON-RPC transports for EVM and Bitcoin and REST transports for TRON and TON behind a single API key. You authenticate once and route to the appropriate transport per chain, so a multi-chain integration does not need separate accounts, keys, or providers for each network.
Sıkça sorulanlar
How do I know whether a chain uses JSON-RPC or REST?
EVM chains and Bitcoin Core use JSON-RPC — a POST envelope with a method field to one endpoint. TRON and TON use REST — typed URL paths such as /wallet/getaccount. The chain family determines the transport, not your preference.
Do I need a separate key for each transport?
No. 1st Node exposes JSON-RPC for EVM and Bitcoin and REST for TRON and TON under a single API key, so one credential covers every chain and transport in your integration.
İlgili araçlar
Bakiye yükle, anahtarını al, yayına çık.
Self servis. Kripto ya da kartla öde. Krediyle ölçümlenir — ağır ilkel yapılar daha pahalı, basitler ucuz.
API anahtarı al