Networks
A consolidated reference for the QoreChain networks — chain identifiers, EVM chain IDs, token denomination, address prefixes, public endpoints, and standard service ports.
Networks at a glance
| Mainnet | Testnet | |
|---|---|---|
| Status | Live | Active testnet |
| Cosmos chain ID | qorechain-vladi | qorechain-diana |
| EVM chain ID (EIP-155) | 9801 (hex 0x2649) | 9800 (hex 0x2648) |
| Live since | 7 June 2026 | 1 July 2026 (continuous since; no reset) |
| Chain version | v3.2.7 (applied at height 4,164,600, 12 November 2026, governance proposal 16). v3.2.6 was applied at height 4,020,000 on 4 November 2026 (proposal 15), v3.2.5 at height 3,906,833 on 29 October 2026, v3.2.4 at height 3,742,566 on 23 October 2026 and v3.2.3 at height 3,662,051 on 20 October 2026 | v3.2.8 (applied at height 9,929,500, 12 November 2026, by governance; v3.2.7 at height 9,594,600 on 6 November, v3.2.6 at height 8,970,638 on 27 October, v3.2.5 at 8,890,800 on 26 October and v3.2.4 at 8,337,253 on 19 October). One release ahead of mainnet; v3.2.8 is not on mainnet yet |
| Block time (measured average) | about 3.1 s | about 1.3 s |
| Release manifest | download.qore.host/mainnet/latest.json | download.qore.host/testnet/latest.json |
| Framework | Cosmos SDK v0.53 | Cosmos SDK v0.53 |
| Minimum gas price | 0.1uqor | 0.1uqor |
| Test tokens | None | Fest tokens fUSD, fETH and fBTC (no value; see Faucet) |
| Connection guide | Connecting to Mainnet | Connecting to Testnet |
Both manifests are the source of truth for the release a fresh node should run. Both networks take coordinated upgrades through governance, so each manifest carries the upgradeHeight of its current release and a minCompatible equal to that release (3.2.7 on mainnet, checked 12 November 2026; 3.2.7 on the testnet when checked on 7 November 2026, which has carried 3.2.8 since 12 November 2026). The testnet takes each release first: it has run v3.2.8 since 12 November 2026 while mainnet has run v3.2.7 since 12 November 2026 (height 4,164,600, governance proposal 16), so a node joining mainnet must keep following its own manifest. On 12 November 2026 the mainnet manifest named the bundle qorechaind-v3.2.7-b3-linux-amd64.tar.gz (99,472,930 bytes, sha256 d4b2f166a75900d2354759b067b3e21c6fbd96003ac056163791cf4b7fb242b5, upgradeHeight 4164600); the testnet manifest named the same bundle on 7 November 2026, while the testnet ran v3.2.7. Read the current bundle name and checksum from the manifest, and see Connecting to Testnet. Never copy a binary between the networks.
Public endpoints
All public endpoints are served over HTTPS.
| Service | Mainnet | Testnet |
|---|---|---|
| Consensus RPC | https://rpc.qore.host | https://rpc-testnet.qore.host |
| Consensus WebSocket | wss://rpc.qore.host/websocket | wss://rpc-testnet.qore.host/websocket |
| Cosmos REST (LCD) | https://api.qore.host | https://api-testnet.qore.host |
| EVM JSON-RPC | https://evm.qore.host | https://evm-testnet.qore.host |
| EVM WebSocket | — | wss://evm-ws-testnet.qore.host |
| SVM JSON-RPC (Solana-compatible, read-only) | https://svm.qore.host | https://svm-testnet.qore.host |
| Block explorer | explore.qore.network | explore.qore.network (toggle to Testnet) |
| Downloads (binary / genesis / snapshot) | download.qore.host | download.qore.host/testnet/latest.json |
The public SVM endpoints are read-only (transaction submission is disabled at the edge); run your own node for SVM writes. For heavy or production workloads, run your own node — see Running a Node. There is no public gRPC endpoint and no public mainnet EVM WebSocket. On the public EVM endpoints, eth_getLogs accepts at most 10,000 blocks per query and txpool_content is disabled (a self-hosted node serves the full namespace); see eth_ Namespace.
If a script gets 403 Forbidden from a public endpoint, set an explicit User-Agent header (Python's default urllib agent is blocked; requests, curl, Node and Go clients work as-is).
Beyond the public endpoints being read-only, the SVM execution lane is currently disabled network-wide for transaction submission (since chain version v3.1.89, 22 August) — this includes submission via your own node, not just the public svm.qore.host / svm-testnet.qore.host endpoints. See SVM Development for details. Use the Cosmos or EVM interfaces until the lane reopens.
Limits on the public endpoints
The public hosts are shared, so they carry limits. Work within them, or run your own node (see Running a Node) for heavier use.
- Request rate. The testnet hosts accept 1,200 requests per 60 seconds from one IP address; above that the address is blocked for 60 seconds.
- SVM JSON-RPC.
getSignaturesForAddressreturns at most 1,000 entries per call, a batch holds at most 100 requests, and a request body is at most 1 MB. - EVM filters. A client can hold at most 16 filters. On the testnet the limit is counted per user; mainnet follows with the v3.2.8 upgrade.
- EVM execution over JSON-RPC. To call a contract without sending a transaction, or to estimate gas, use
eth_callandeth_estimateGason the EVM JSON-RPC host (evm.qore.host,evm-testnet.qore.host). The REST routes under/cosmos/evm/vm/v1/foreth_call,estimate_gasand tracing, and their gRPC-web forms, are not available on the public endpoints and answer 403. The debug and trace APIs are not offered on the public endpoints either: run your own node for them. Cosmos transaction simulation (/cosmos/tx/v1beta1/simulate) stays available, so wallets that estimate gas by simulation, Keplr included, keep working.
Token and addresses
| Item | Value |
|---|---|
| Display denom | QOR |
| Base denom | uqor (1 QOR = 10⁶ uqor) |
| Decimals by interface | Cosmos 6 (uqor) · EVM 18 (wei-style; 1 uqor = 10¹² wei) · SVM 9 (lamports; 1 uqor = 1,000 lamports) |
| HD coin type (BIP-44) | 118 |
| Bech32 account prefix | qor (e.g. qor1...) |
| Bech32 validator prefix | qorvaloper (e.g. qorvaloper1...) |
The three interfaces expose one unified native-QOR balance: the same key controls the same funds under its qor1... (Cosmos), 0x... (EVM), and base58 (SVM) address forms.
Standard ports
These are the standard service ports exposed by a QoreChain node you run yourself.
| Service | Port |
|---|---|
| Cosmos RPC | 26657 |
| P2P | 26656 |
| REST / API | 1317 |
| gRPC | 9090 |
| EVM JSON-RPC | 8545 |
| EVM JSON-RPC (WebSocket) | 8546 |
| SVM (Solana-compatible) JSON-RPC | 8899 |
| Prometheus metrics | 26660 |
Endpoints and access
- For node connection, peers, genesis, and snapshots, follow Connecting to Mainnet or Connecting to Testnet.
- For programmatic access from an application, use the QoreChain SDK, which resolves network configuration for you.
- The public block explorer is at explore.qore.network; the Dashboard at dashboard.qorechain.io includes its own explorer view, and the testnet Faucet is reachable there (see Dashboard Faucet).
- These docs are published at docs.qorechain.io.
Add to MetaMask
To add a QoreChain network to an EVM wallet such as MetaMask, use the EVM chain IDs above — 9801 for mainnet with https://evm.qore.host, and 9800 for testnet with https://evm-testnet.qore.host — with https://explore.qore.network as the block-explorer URL. See Wallet Setup for the step-by-step walkthrough.
Related
- Connecting to Mainnet — join the live
qorechain-vladinetwork. - Connecting to Testnet — join the Diana testnet.
- Exchange & Integrator Guide — deposits, withdrawals, and node operations for integrators.
- Chain Parameters — canonical chain configuration.
- SDK Overview — resolve network configuration from code.