Connecting to Testnet
Join the live QoreChain Diana testnet by configuring your node with the correct genesis file, peers, and network settings.
This page covers the qorechain-diana testnet (EVM chain ID 9800). Mainnet (qorechain-vladi, EVM chain ID 9801) has been live since 7 June 2026 (release v3.2.7 since 12 November 2026; the testnet is one release ahead) and has its own dedicated Connecting to Mainnet page with separate genesis, peers, and connection details. The testnet has run v3.2.8 since 12 November 2026 (it ran v3.2.7 from 6 November and v3.2.6 from 27 October; mainnet applied v3.2.6 on 4 November 2026 and v3.2.7 on 12 November 2026); its release manifest is at download.qore.host/testnet/latest.json.
Public Endpoints
If you only need to query the testnet or broadcast transactions, use the public endpoints:
| Service | URL |
|---|---|
| Consensus RPC | https://rpc-testnet.qore.host (WebSocket: wss://rpc-testnet.qore.host/websocket) |
| Cosmos REST (LCD) | https://api-testnet.qore.host |
| EVM JSON-RPC | https://evm-testnet.qore.host (chain ID 9800) |
| EVM WebSocket | wss://evm-ws-testnet.qore.host |
| SVM JSON-RPC (read-only) | https://svm-testnet.qore.host |
| Block explorer | explore.qore.network (toggle to Testnet) |
Testnet QOR is available from the Dashboard Faucet, which can also send the testnet-only Fest test tokens (fUSD, fETH, fBTC; no value).
The public hosts are shared and carry limits (request rate, SVM RPC sizes, EVM filters); eth_call and gas estimation go through the EVM JSON-RPC host. See Limits on the public endpoints.
Install
The canonical source of truth for the current testnet binary, genesis, peers and state-sync trust point is the testnet manifest, refreshed live at https://download.qore.host/testnet/latest.json. It has the same layout as the mainnet manifest, so the install steps are the same — fetch it and use its values rather than hardcoding a version or checksum:
curl -s https://download.qore.host/testnet/latest.json -o latest.json
jq -r '.version, .minCompatible, .upgradeHeight' latest.json
BINARY_URL=$(jq -r .binary.url latest.json)
BINARY_SHA256=$(jq -r .binary.sha256 latest.json)
curl -fsSL "$BINARY_URL" -o qore.tgz
echo "${BINARY_SHA256} qore.tgz" | sha256sum -c -
tar xzf qore.tgz
sudo install -m0755 qorechaind /usr/local/bin/
sudo mkdir -p /opt/qorechain/lib && sudo cp lib/*.so /opt/qorechain/lib/
export LD_LIBRARY_PATH=/opt/qorechain/lib
qorechaind init my-node --chain-id qorechain-diana
The testnet takes coordinated upgrades through governance proposals, so its manifest carries an upgradeHeight and minCompatible equals the current version. A node that joins now needs the release in the manifest. Since 12 November 2026 the testnet release is v3.2.8 (height 9,929,500); read version, minCompatible, upgradeHeight and the bundle name, size and sha256 from the manifest. On 12 November 2026 (v3.2.8) the manifest read version 3.2.8, minCompatible 3.2.8 and upgradeHeight 9929500, and its binary was qorechaind-v3.2.8-b3-linux-amd64.tar.gz (107,091,599 bytes, sha256 ead3f3e869d1fe52229b683d3d7c206fca7e56d6f984a2b721f3fb21cb0b9954; verify the sha256 before you run the binary). For reference, on 7 November 2026 (v3.2.7) the manifest read version 3.2.7, minCompatible 3.2.7 and upgradeHeight 9594600, and its binary was qorechaind-v3.2.7-b3-linux-amd64.tar.gz (99,472,930 bytes, sha256 d4b2f166a75900d2354759b067b3e21c6fbd96003ac056163791cf4b7fb242b5; read the values from the manifest again and verify the sha256 before you run the binary). Its note says the release includes post-quantum multisig, calibrated post-quantum verification gas, cross-VM improvements and more reliable JSON-RPC block reads. Keep the system clock NTP-synchronised.
Node still on v3.2.7. It stops at height 9,929,500. Replace qorechaind and copy the whole lib/ folder of the v3.2.8 bundle (it adds one library next to the existing ones), then start it again: the state is kept and no resync is needed.
| Release | Testnet height | Date applied |
|---|---|---|
| v3.2.2 | 6,905,034 | 2 October 2026 |
| v3.2.3 | 8,003,746 | 15 October 2026 |
| v3.2.4 | 8,337,253 | 19 October 2026 |
| v3.2.5 | 8,890,800 | 26 October 2026 |
| v3.2.6 | 8,970,638 | 27 October 2026 (16:58 UTC) |
| v3.2.7 | 9,594,600 | 6 November 2026 (about 15:00 UTC) |
| v3.2.8 | 9,929,500 | 12 November 2026 (about 03:35 UTC) |
The testnet takes each release before mainnet. Mainnet applied v3.2.4 at height 3,742,566 on 23 October 2026, v3.2.5 at height 3,906,833 on 29 October 2026 (governance proposal 14) v3.2.6 at height 4,020,000 on 4 November 2026 (governance proposal 15) and v3.2.7 at height 4,164,600 on 12 November 2026 (governance proposal 16). Mainnet is therefore one release behind: the testnet has run v3.2.8 since 12 November 2026, which mainnet has not applied. The manifests are separate, so never copy a binary between the two networks (the v3.2.8 additions are listed in Version History).
Download Genesis
Replace your local genesis file with the official testnet genesis, using the URL and SHA-256 from the manifest fetched above:
GENESIS_URL=$(jq -r .genesis.url latest.json)
GENESIS_SHA256=$(jq -r .genesis.sha256 latest.json)
curl -fsSL "$GENESIS_URL" -o ~/.qorechaind/config/genesis.json
echo "${GENESIS_SHA256} $HOME/.qorechaind/config/genesis.json" | sha256sum -c -
The same file is also served live by the chain itself:
curl -s https://rpc-testnet.qore.host/genesis | jq '.result.genesis' > /tmp/genesis-live.json
This file defines the initial state of the Diana testnet, including the validator set, token allocations, and module parameters.
Diana has been running continuously since 1 July 2026 and is upgraded through governance proposals like mainnet. The testnet is a staging network and can be reset without notice: if your node stops syncing, check the manifest and the Discord announcements, then re-download the genesis and start from a fresh data directory. The public sentry keeps only recent blocks, so a new node should state-sync (below) rather than replay from genesis.
Configure Peers
Read the current peer and seed lists from the manifest rather than hardcoding node IDs and hosts:
PEERS=$(jq -r '.peers | join(",")' latest.json)
SEEDS=$(jq -r '.seeds | join(",")' latest.json)
Open ~/.qorechaind/config/config.toml and set the persistent_peers (and seeds) fields to those values:
persistent_peers = "<value of $PEERS>"
seeds = "<value of $SEEDS>"
Also set the fee floor in ~/.qorechaind/config/app.toml (the testnet uses the same 0.1uqor minimum gas price as mainnet):
minimum-gas-prices = "0.1uqor"
Recommended Settings
A full node does not choose the block time — validators do (the testnet currently produces a block about every 1.3 seconds). Leave the consensus timeouts at their defaults unless you operate a validator and have been given values by the validator group. A useful mempool setting for a public RPC node, in config.toml:
[mempool]
size = 5000
Fast Bootstrap (State Sync)
The manifest's stateSync field carries a trust height/hash pair refreshed regularly:
TRUST_HEIGHT=$(jq -r .stateSync.trustHeight latest.json)
TRUST_HASH=$(jq -r .stateSync.trustHash latest.json)
Set the [statesync] section of config.toml with those values and the rpcServers from the manifest — see Running a Node for the full workflow.
Start Node
Launch your node to begin syncing with the network:
./qorechaind start
The node connects to peers and begins downloading blocks (from genesis, or from the trust height if you use state sync). Initial sync time depends on the current chain height and your network speed.
Check Sync Status
Verify that your node is catching up to the latest block:
curl localhost:26657/status | jq '.result.sync_info.catching_up'
true— The node is still syncing. Wait for it to catch up.false— The node is fully synced and processing new blocks.
You can also check the latest block height:
curl localhost:26657/status | jq '.result.sync_info.latest_block_height'
Monitoring
QoreChain exposes several endpoints for monitoring node health and performance.
Prometheus Metrics
Raw metrics are available at:
http://localhost:26660/metrics
These metrics can be scraped by any Prometheus-compatible collector.
Grafana Dashboards
If running via Docker Compose, Grafana is available at:
http://localhost:3001
On first login, set your own credentials when prompted — do not leave the defaults in place. Pre-configured dashboards display block production, transaction throughput, peer connections, and resource usage.
REST Health Check
The REST API provides a quick status endpoint:
http://localhost:1317
Ports Reference
| Port | Protocol | Description |
|---|---|---|
26657 | TCP | RPC — query and broadcast transactions |
26656 | TCP | P2P — peer-to-peer network communication |
1317 | HTTP | REST API — query chain state via HTTP |
9090 | gRPC | gRPC API — programmatic chain access |
8545 | HTTP | EVM JSON-RPC — Ethereum-compatible RPC (chain ID 9800) |
8546 | WebSocket | EVM WebSocket — real-time EVM event subscriptions |
8899 | HTTP | SVM RPC — Solana-compatible RPC (reads only; the SVM transaction lane is disabled) |
26660 | HTTP | Prometheus metrics endpoint |
Next Steps
- Wallet Setup — Configure a wallet for the testnet
- Your First Transaction — Send your first QOR transfer