https://rpc.shyft.network/

Shyft Mainnetevm

shyft.network· rpc compare ↔

Posture score

Speed score

TLS version

TLS 1.3

Cipher

TLS_AES_256_GCM_SHA384

KEX group

classical

PQ class

Classical only

ALPN

http/1.1

Cert expires in

25d

Session resumed

yes

TLS handshake

239ms

Resumption

250ms

TTFB

1.23s

RPC block height

21,633,732

TLS handshake

VersionTLS 1.3

CipherTLS_AES_256_GCM_SHA384

KEX groupclassical

ALPNhttp/1.1

PQ classClassical only

Handshake239ms

Resumed?yes · 250ms

OCSP stapledno

SCTs presentno

Certificate chain

Subjectrpc.shyft.network

IssuerYR2

Key typeRSA-2048

Chain length3

SANs*.rpc.shyft.network, rpc.shyft.network

Not before2026-08-06

Not after2026-11-04

Days to expiry25d

Chain SHA-2567538274ff7af35c6…

Misconfigurations

OCSP stapling not enabled no_ocsp_staple

Grades

Posture

B83

Speed

D64

Certificate

100

TLS profile

Post-quantum

RPC reachability

100

Endpoint identity

URL

https://rpc.shyft.network/

Host

rpc.shyft.network

Chain

Shyft Mainnet

Chain ID

7341

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

Classical only

Key exchange

Cipher

TLS_AES_256_GCM_SHA384

Last seen

2026-10-10T05:08:47.489102729Z

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

Scan reportschema rpcscan-report · captured 2026-10-10T05:57:43.966Z

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.