> For the complete documentation index, see [llms.txt](https://docs.qms.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qms.finance/for-developers/network-and-rpc.md).

# Network and RPC

Use the following configuration to connect your Ethereum tools to QMS Testnet.

|                  | QMS Testnet                          |
| ---------------- | ------------------------------------ |
| Network name     | QMS Testnet                          |
| Chain ID         | 19480 (`0x4c18`)                     |
| JSON-RPC (HTTPS) | `https://rpc.testnet.qms.finance`    |
| WebSocket        | `wss://rpc.testnet.qms.finance`      |
| Currency symbol  | QMS                                  |
| Block time       | 10 s (target)                        |
| Block explorer   | <https://testnet.qmsscan.io>         |
| Faucet           | <https://faucet.testnet.qms.finance> |
| Status page      | <https://status.testnet.qms.finance> |

QMS Testnet is registered in the [ethereum-lists chain registry](https://github.com/ethereum-lists/chains/blob/master/_data/chains/eip155-19480.json), which Chainlist and wallets read, under the short name `qmstest`.

Check that you are talking to the right chain:

```bash
curl -s -X POST -H 'content-type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}' \
  https://rpc.testnet.qms.finance
```

```json
{"jsonrpc":"2.0","id":1,"result":"0x4c18"}
```

## The public endpoint

The RPC endpoint above is public and shared. It is rate limited to 50 requests per second per client address, with bursts of up to 200 requests, and answers HTTP 429 beyond that. Each client address can hold up to 20 WebSocket connections open at once. It is intended for development and testing, not for production traffic. There are no third-party RPC providers for QMS Testnet yet.

If the endpoint does not respond, check the [status page](https://status.testnet.qms.finance) before assuming a problem on your side.

## JSON-RPC API

QMS exposes the standard Ethereum JSON-RPC API of its execution client, a fork of Reth. The public endpoint serves the `eth`, `net`, and `web3` namespaces; `debug` and `trace` are not available on it. Two things behave differently from Ethereum, both because of what the current release does not yet include:

* `eth_sendRawTransaction` and `eth_sendRawTransactionSync` reject type-3 (blob) transactions with `-32003 transaction type not supported`.
* Any method called with the `safe` or `finalized` block tag returns the genesis state, until the finality layer is enabled.

[EVM Compatibility](/for-developers/evm-compatibility.md) has the details.

## Block explorer

The explorer is a modified Blockscout. Its API and contract verification are available at their usual paths; see [Deploy a smart contract](/for-developers/deploy-a-smart-contract.md) for verification. Each block page also shows the visible trace of proof-of-useful-work: the hash of the QUBO instance that was solved, the winning solution with its objective value, and a download of the full instance in Matrix Market format (`.mtx.gz`).