JSON-RPC reference

The Quantum Chain node exposes a standard JSON-RPC 2.0 interface over HTTP and WebSocket. All methods in the Ethereum eth_* namespace are also available under the qc_* namespace. The qc_* variant is recommended for Quantum Chain integrations.

Every qc_* method has an identical eth_* counterpart. If your tooling only supports eth_*, it works the same way.

Connecting

HTTP

curl -X POST https://api.quantumapi.io/v1/rpc \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"qc_blockNumber","params":[],"id":1}'

WebSocket

wscat -c wss://api.quantumapi.io/v1/rpc
> {"jsonrpc":"2.0","method":"qc_blockNumber","params":[],"id":1}

Enabling RPC modules

By default, the node only exposes net and web3 modules. Enable additional modules with CLI flags:

geth --http --http.api eth,qc,net,web3,txpool --ws --ws.api eth,qc,net,web3

Namespaces

Namespace	Description
`qc`	Quantum Chain native: accounts, blocks, transactions, gas, execution
`eth`	Ethereum-compatible alias (identical to `qc`)
`net`	Network info: peer count, version, listening status
`web3`	Utilities: client version, SHA3
`txpool`	Transaction pool inspection
`debug`	Debugging and tracing
`admin`	Node administration and peer management
`personal`	Account management (unlock, sign)

Request format

Every request follows JSON-RPC 2.0:

{
  "jsonrpc": "2.0",
  "method": "qc_blockNumber",
  "params": [],
  "id": 1
}

Block number tags

Several methods accept a block identifier instead of a number:

Tag	Meaning
`"latest"`	Most recent mined block
`"pending"`	Pending state/transactions
`"earliest"`	Genesis block
`"finalized"`	Most recent finalized block
`"safe"`	Most recent safe block

Reference pages

Blocks

Chain ID, block number, headers, block lookups, uncle queries

Accounts

Balances, code, storage, proofs, receipts

Transactions

Send, query, sign, receipts, pending pool

Gas & fees

Gas price, priority fee, fee history, estimation

Execution

Read-only calls, access lists, sync status

Get started

Operate

Build