RPCScan
4,976 networks tracked8,031 RPC URLsRequestStatus
Companion site:ExplorerScan ↗Block explorer directory with per-provider drill-downs and TLS posture per host
BitYuan Mainnet

https://node2.bityuan.com/eth

BitYuan Mainnetevmbityuan.com· node2compare ↔
Posture score
72
Speed score
39
TLS version
TLS 1.2
Cipher
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
KEX group
classical
PQ class
Classical only
ALPN
http/1.1
Cert expires in
3d
Session resumed
yes
TLS handshake
520ms
Resumption
336ms
TTFB
1.79s
RPC block height
48,416,585
TLS handshake
VersionTLS 1.2
CipherTLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
KEX groupclassical
ALPNhttp/1.1
PQ classClassical only
Handshake520ms
Resumed?yes · 336ms
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subjectnode2.bityuan.com
IssuerZeroSSL ECC DV SSL CA 2
Key typeECDSA-P-256
Chain length3
SANsnode2.bityuan.com
Not before2026-08-21
Not after2026-11-19
Days to expiry3d
Chain SHA-256547cec6fca57a9a6…
Modern posture
HSTSno header
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECunsigned
CAA recordsnone published
Must-staplenot declared
Grades
Posture
C72
Speed
F39
Certificate
80
TLS profile
68
Post-quantum
40
RPC reachability
100
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
https://node2.bityuan.com/eth
Host
Chain ID
2999
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
Classical only
Key exchange
-
Cipher
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
Last seen
2026-11-16T18:26:00.637333039Z
History (30 days)
no history

Chain peer ranking

This URL is fastest right now
no
Fastest p50 latency
1.51s
Latest block height
-

Using this RPC

tabs 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://node2.bityuan.com/eth' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-11-16T22:29:00.449Z
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.