Oasis Sapphire RPC endpoints: free public URLs by latency
HTTP round-trip latency for eth_getBlockByNumber against every free, no-key public Oasis Sapphire RPC endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , Oasis Foundation is the only free public Oasis Sapphire RPC endpoint measured, at 138 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/oasis-sapphire-rpc.
Companion page
Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →
Oasis Sapphire (chain 23294) is the only production confidential EVM, running smart contracts inside Intel SGX widely used execution environments to keep state and inputs private by default. It is part of the Oasis Network, ROSE gas token bridged from the consensus layer. The Oasis Foundation's sapphire.oasis.io provides keyless access probed every 60 seconds from three regions.
Methodology
Oasis Sapphire: 1 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Oasis Foundation leads at 138 ms; the chain-official endpoint measures 138 ms. We measure the round-trip latency of a single, identical RPC call (`eth_getBlockByNumber`) against every no-key public Oasis Sapphire endpoint that sustains continuous probing, 1 provider at launch, every 60 seconds, from us-east, eu-west and Singapore. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) so the leaderboard rewards sustained availability rather than fast error messages. The cross-chain view lives on the parent `rpc-capabilities` benchmark; this page is the Oasis Sapphire-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: `{"jsonrpc":"2.0","id":<rotating>,"method":"eth_getBlockByNumber","params":["latest",false]}`. Plain HTTP POST, identical for every endpoint, no API key in any request.
- 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 Oasis Sapphire-scoped view of the same harness, with the same exclusion rules.
- Chain scope: every query on this page is pinned to `chain="oasis-sapphire"`. Provider coverage today: 1 no-key endpoints (Oasis Foundation).
Results: 1 free public Oasis Sapphire RPC endpoint ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | Oasis FoundationOasis Foundation's Sapphire public RPC | 138 ms | 160 ms | 209 ms | 100.00% (n=4322) |
Frequently asked
Which Oasis Sapphire RPCs work without an API key?
1 endpoint sustains continuous keyless probing at launch: Oasis Foundation. Every listed endpoint was live-verified before inclusion.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities