RPCScan
- networks tracked- RPC URLsRequestStatus
Companion site:ExplorerScan ↗Block explorer directory with per-provider drill-downs and TLS posture per host
Edgeware EdgeEVM Mainnet

https://saigon-testnet.roninchain.com/rpc

Edgeware EdgeEVM Mainnetevmroninchain.com· saigon-testnetcompare ↔● fastest right now
Posture score
73
Speed score
70
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
-
PQ class
Unknown
ALPN
h2
Cert expires in
35d
Session resumed
yes
TLS handshake
107ms
Resumption
61ms
TTFB
714ms
RPC block height
56,169,437
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX group-
ALPNh2
PQ classUnknown
Handshake107ms
Resumed?yes · 61ms
OCSP stapledno
SCTs presentno
Certificate chain
Subjectroninchain.com
IssuerWE1
Key typeECDSA-P-256
Chain length3
SANsroninchain.com, *.roninchain.com
Not before2026-08-16
Not after2026-11-14
Days to expiry35d
Chain SHA-256d8cf2e4f567b574b…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
C73
Speed
C70
Certificate
100
TLS profile
95
Post-quantum
0
RPC reachability
100
Endpoint identity
URL
https://saigon-testnet.roninchain.com/rpc
Host
Chain ID
2021
VM
evm
Platform type
chain
Live probe (last 24 h)
Probes attempted
-
Successful
-
Success rate
-
Median p50
-
Median p95
-
Latest bucket
-
TLS posture (post-quantum)full history →
Class
Unknown
Key exchange
-
Cipher
TLS_AES_128_GCM_SHA256
Last seen
2026-10-10T08:23:58.714517224Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
YES
Fastest p50 latency
714ms
Latest block height
-
Using this RPCtabs auto-fill the URL + chain ID
JSON-RPC eth_chainId, which verifies the endpoint is alive and reports the chain ID.
curl -X POST 'https://saigon-testnet.roninchain.com/rpc' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T08:27:50.452Z
SHA-256 of canonical content
computed in your browser
computing…

The hash covers every field above the JSON serialization with sorted keys. Re-running this computation against the downloaded artifact must produce the same hash; that's how RPCScan's future on-chain proofs (rpcscanchain) will let anyone verify a published snapshot wasn't tampered with.