cheqd RPC endpoints: free public URLs by latency
HTTP round-trip latency for Tendermint /status queries against every available public cheqd (cheqd-mainnet-1) endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , NodeStake has the lowest median latency of the 3 free public cheqd RPC endpoints measured, 87 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/cheqd-rpc. 3 public endpoints, no key: rpc.cheqd.nodestake.org, cheqd-rpc.publicnode.com, rpc.cheqd.net. Full URLs with their 24h median are listed below.
Companion page
Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →
cheqd is a purpose-built Cosmos SDK blockchain (chain ID cheqd-mainnet-1) for decentralized identity, enabling self-sovereign identity (SSI) and verifiable credentials at scale. The cheqd-mainnet-1 network anchors DIDs and credential schemas used by enterprises, governments, and developers building trust infrastructure. The chain uses the standard Tendermint RPC interface; block height is fetched via the /status endpoint. Public keyless RPC nodes are provided by the cheqd official team, PublicNode, and NodeStake. Every provider was live-verified with consecutive block-height probes at launch.
Methodology
cheqd: 3 free public RPC endpoints answering `GET /status` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. NodeStake leads at 87 ms; the chain-official endpoint measures 309 ms. We measure the round-trip latency of a Tendermint /status query against every available public cheqd endpoint that sustains continuous probing: 3 providers live today, every 60 seconds, from us-east, eu-west and Singapore. Each provider is probed via a GET /status request from which the block number is extracted. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) with a Cosmos-scaled staleness gap (40 blocks, around 4 min at 6 s/block). The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the cheqd-scoped answer with per-region breakdowns as a first-class dimension.
Results: 3 free public cheqd RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | NodeStake | 87 ms | 302 ms | 1.28 s | 98.47% |
| 2 | PublicNode | 93 ms | 209 ms | 373 ms | 99.98% |
| 3 | cheqd | 309 ms | 338 ms | 380 ms | 100.00% |
Public cheqd RPC endpoints measured
The 3 no-key endpoints answering our probes today, with their current 24h median. Paste one into a wallet or a client as is: no signup, no key. Private providers (API key) are never listed with a URL.
NodeStakehttps://rpc.cheqd.nodestake.org87 ms98.5%
PublicNodehttps://cheqd-rpc.publicnode.com:44393 ms100.0%
cheqdhttps://rpc.cheqd.net309 ms100.0%
Median round-trip and success rate over the last 24 hours across the probe regions; the ranked table above carries p90, p99 and the per-region split.
Frequently asked
Which cheqd RPC endpoints work without an API key?
3 endpoints are probed on this chain: cheqd official (rpc.cheqd.net), PublicNode (cheqd-rpc.publicnode.com), and NodeStake (rpc.cheqd.nodestake.org). Every listed endpoint was live-verified before inclusion.
What is cheqd and why does its RPC latency matter?
cheqd is a Cosmos SDK blockchain built for decentralized identity (DID) and verifiable credentials. DID resolution, verifiable credential anchoring, and CHEQ token transfers all depend on RPC availability. Applications using the cheqd DID method resolve identifiers via RPC, making latency directly visible to end users and credential verifiers.
What is the CHEQ token?
CHEQ is the native staking and governance token of the cheqd network (denominated as ncheq on-chain). It is used to pay for DID writes, credential schema anchoring, and on-chain governance participation.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities