# Litecoin

> Litecoin Mainnet and Testnet through RPC Gateway, including the provider gap on Litecoin Testnet and the manual Endpoint workaround.

Canonical page: https://rpc.aurpay.net/docs/chains/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](https://rpc.aurpay.net/docs/chains/bitcoin.md).

## 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](https://rpc.aurpay.net/docs/providers/alchemy.md) | Yes | Yes |
| [QuickNode](https://rpc.aurpay.net/docs/providers/quicknode.md) | Yes | Yes |
| [Chainstack](https://rpc.aurpay.net/docs/providers/chainstack.md) | Yes | No |
| [dRPC](https://rpc.aurpay.net/docs/providers/drpc.md) | No | No |
| [Tenderly](https://rpc.aurpay.net/docs/providers/tenderly.md) | 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](https://rpc.aurpay.net/docs/endpoints.md#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](https://rpc.aurpay.net/docs/endpoint-free-rpc.md) for the parameter table.

## Verify the network

```bash
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](https://rpc.aurpay.net/docs/providers.md) for synchronization behavior and [JSON-RPC](https://rpc.aurpay.net/docs/json-rpc.md) for the request contract.