Public services

The test network's public endpoints. Every one of them is a feature of the Requant node, so anyone can run the same services on their own node.

Explorer

Two explorers read the same chain:

• requant.network/explorer: blocks, transactions, addresses, measured network rate over 24 hours, and the mining pool. It indexes the chain from a reference node and marks stale data clearly.
• The node's built-in explorer: every node started with --explorer serves blocks, transactions, addresses, a network page with peers, mempool and watchman events, the pool and the faucet, plus /health and the public API.

Faucet

• Sends 10 RQT to a test-network address, at most once a day per address and per client, within a daily budget.
• Coins come from the faucet's own confirmed and pending outputs; anyone can top it up at trq1q8pqnx3uqer6jcxszen4tg3hylh5q645ae23yvra62a2nu98slqaqvvyume.
• A node runs a faucet with --faucet-key FILE --faucet-amount 10 --faucet-daily 1000.

Wallet gateway

The Web Wallet, the wallet apps and the extension reach the network through https://requant.network/wallet-api/. It forwards a fixed set of read methods (getinfo, getblock, gettx, utxos, history) and sendtx for signed transactions of up to 100,000 bytes, keeps the node's RPC credentials on the server and never accepts passwords or keys. Limits: 240 reads and 10 broadcasts per client per minute.

Health

GET /health on any node with an explorer returns its status as JSON, and HTTP 503 when the node has no peers, has seen no block for 20 minutes or is still syncing. It is meant for uptime monitors and load balancers.

Privacy

Public services see what you ask them: which addresses you look up and which transactions you send, with your IP address. For privacy and for trust in the answers, run your own node.