RPCsUpdated

Waves RPC endpoints: free public URLs by latency

HTTP round-trip latency for GET /blocks/last against every available public Waves node, audited every 60 seconds from 3 regions.

TL;DR. As of , Waves.Exchange has the lowest median latency of the 3 free public Waves RPC endpoints measured, 143 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/waves-rpc. 3 public endpoints, no key: nodes.wx.network, nodes.waves.exchange, nodes.wavesnodes.com. 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 →

Waves is a proof-of-stake blockchain optimised for decentralised finance and token creation, producing one block approximately every 60 seconds. The chain exposes a REST API at /blocks/last returning the latest committed block height as a plain integer. Public REST endpoints are available without an API key from the Waves Foundation, Waves.Exchange and nodes.waves.exchange. Every provider was live-verified with consecutive block probes at launch.

Methodology

Waves: 3 free public RPC endpoints answering `GET /blocks/last` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Waves.Exchange (tied) leads at 143 ms. We measure the round-trip latency of a single REST call (GET /blocks/last) against every available public Waves node that sustains continuous probing: 3 providers live today, every 60 seconds, from us-east, eu-west and Singapore. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) with a Waves-scaled staleness gap (5 blocks, around 5 min at 60 s/block). The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the Waves-scoped answer with per-region breakdowns as a first-class dimension.

  • Cadence: every 60 seconds per provider, from each of 3 probe regions (us-east Virginia, eu-west Amsterdam, sgp Singapore). Headline p50/p90/p99 aggregate across all 3 regions via Prometheus avg(quantile_over_time(...)); per-region breakdowns are first-class on this page via the region tabs.
  • Payload: HTTP GET /blocks/last. Plain REST call. The response carries height as a plain integer.
  • Latency measurement, call-result classification (`ok`, `http_err`, `jsonrpc_err`, `stale`, `timeout`) and the archive-depth audit follow the cluster method documented on [rpc-capabilities](openchainbench.com/benchmarks/rpc-capabilities#methodology); this page is the Waves-scoped view of the same harness, with the same exclusion rules.
  • Chain scope: every query on this page is pinned to chain=waves. Provider coverage today: 3 endpoints (Waves Foundation, Waves.Exchange x2).

Results: 3 free public Waves RPC endpoints ranked by p50 latency (24h, 3 regions)

Waves RPC endpoints: free public URLs by latency: RPC latency per provider (p50, 24h).
№Providersp50p90p99Success
1Waves.ExchangeWaves.Exchange public node (nodes.wx.network), keyless143 ms256 ms888 ms98.77% (n=4318)
2Waves Exchange NodeWaves Exchange public node (nodes.waves.exchange), keyless143 ms269 ms1.09 s98.73% (n=4317)
3Waves FoundationWaves Foundation official public nodes, keyless145 ms294 ms702 ms98.47% (n=4320)

Public Waves 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.

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 Waves RPC endpoints work without an API key?

3 endpoints are probed on this chain: Waves Foundation nodes (nodes.wavesnodes.com), Waves.Exchange (nodes.wx.network) and WavesExchange (nodes.waves.exchange). Every listed endpoint was live-verified with a blocks/last call returning a parsable height before inclusion.

Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities