Litecoin
Litecoin reaches the Gateway as Litecoin Core-style JSON-RPC over HTTP for chain, block, and transaction reads. Its native asset is LTC, and it shares the UTXO request set with Bitcoin.
Networks and hosts
| Network | JSON-RPC Host |
|---|---|
| Mainnet | ltc-jsonrpc |
| Testnet | ltc-testnet-jsonrpc |
Litecoin uses no EVM chain ID. Copy the deployed Access Point from the dashboard and keep the two networks in separate Gateways.
Provider coverage
Litecoin has the narrowest Provider coverage in the catalog. dRPC synchronizes no Litecoin networks at all, and Chainstack covers Mainnet only — Litecoin Testnet is the single combination missing from the otherwise complete Chainstack integration.
| Provider | Mainnet | Testnet |
|---|---|---|
| Alchemy | Yes | Yes |
| QuickNode | Yes | Yes |
| Chainstack | Yes | No |
| dRPC | No | No |
| Tenderly | No | No |
If your account runs on Chainstack, register the Litecoin Testnet node as a manual Endpoint: pick the chain, network, and protocol at creation time, set the authentication the node expects, and run the health probe before attaching it to the Route. Add a manual Endpoint covers the flow, and an Account can hold up to 20 undeleted manual Endpoints.
Reads without an Endpoint
The UTXO cached set applies to Litecoin as well: getblockchaininfo with parameters omitted or [], getblockhash with one non-negative height, and getblock with a block hash and verbosity 3. Any other verbosity or parameter form continues through the Route to an Endpoint. See Endpoint-free RPC for the parameter table.
Verify the network
curl '<litecoin_access_point>' \
-H 'Authorization: Bearer <app_api_key>' \
-H 'Content-Type: application/json' \
--data '{"jsonrpc":"2.0","id":1,"method":"getblockchaininfo","params":[]}'chain reads main on Mainnet and is normally test on Testnet. Because the shared cache can answer this call, confirm your own upstream through its health check and Route state as well.
Coverage boundary
One JSON-RPC 2.0 object per HTTP POST. Wallet methods, address indexes, pruning depth, and how much history a node retains are properties of the upstream configuration. Manage wallets on the node itself and give Mainnet and Testnet independent Routes.
See Providers for synchronization behavior and JSON-RPC for the request contract.