https://sepolia-rpc.zkbase.app

ZKBase Sepolia Testnetevm

zkbase.app· sepolia-rpc compare ↔● PQ hybrid

Posture score

Speed score

TLS version

TLS 1.3

Cipher

TLS_AES_128_GCM_SHA256

KEX group

X25519MLKEM768

PQ class

PQ hybrid

ALPN

Cert expires in

77d

Session resumed

yes

TLS handshake

23ms

Resumption

14ms

TTFB

RPC block height

Prober warning: phase_b: Post "https://sepolia-rpc.zkbase.app": http2: timeout awaiting response headers

TLS handshake

VersionTLS 1.3

CipherTLS_AES_128_GCM_SHA256

KEX groupX25519MLKEM768

ALPNh2

PQ classPQ hybrid

Handshake23ms

Resumed?yes · 14ms

OCSP stapledno

SCTs presentno

Certificate chain

Subjectzkbase.app

IssuerWE1

Key typeECDSA-P-256

Chain length3

SANszkbase.app, *.zkbase.app

Not before2026-09-26

Not after2026-12-25

Days to expiry77d

Chain SHA-256f71c20da6cb46920…

Misconfigurations

OCSP stapling not enabled no_ocsp_staple

Grades

Posture

C78

Speed

Certificate

100

TLS profile

Post-quantum

RPC reachability

Endpoint identity

URL

https://sepolia-rpc.zkbase.app

Host

sepolia-rpc.zkbase.app

Chain

ZKBase Sepolia Testnet

Chain ID

1789

evm

Platform type

chain

Sibling RPCs

view all on chain page →

Live probe (last 24 h)

Probes attempted

Successful

Success rate

Median p50

Median p95

Latest bucket

TLS posture (post-quantum)full history →

Class

PQ hybrid

Key exchange

X25519MLKEM768

Cipher

TLS_AES_128_GCM_SHA256

Last seen

2026-10-08T15:58:14.218427326Z

History (30 days)

no history

Chain peer ranking

This URL is fastest right now

Fastest p50 latency

Latest block height

Current fastest URL

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://sepolia-rpc.zkbase.app' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'

Scan reportschema rpcscan-report · captured 2026-10-10T05:59:13.816Z

SHA-256 of canonical content

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.