https://evm-rpc-story.josephtran.xyz

Story Testnetevm

josephtran.xyz· evm-rpc-story compare ↔

Posture score

Speed score

TLS version

TLS 1.3

Cipher

TLS_AES_256_GCM_SHA384

KEX group

classical

PQ class

Classical only

ALPN

Cert expires in

76d

Session resumed

yes

TLS handshake

86ms

Resumption

78ms

TTFB

492ms

RPC block height

TLS handshake

VersionTLS 1.3

CipherTLS_AES_256_GCM_SHA384

KEX groupclassical

ALPN-

PQ classClassical only

Handshake86ms

Resumed?yes · 78ms

OCSP stapledno

SCTs presentno

Certificate chain

Subjectpachucos.com

IssuerYE1

Key typeECDSA-P-256

Chain length4

SANs*.0gchain.josephtran.xyz, *.154vps5.josephtran.xyz, *.95q7dzhwy7.world +87

Not before2026-09-26

Not after2026-12-25

Days to expiry76d

Chain SHA-2567f9de19034c49a39…

Misconfigurations

ALPN not negotiated no_alpn
OCSP stapling not enabled no_ocsp_staple

Grades

Posture

D63

Speed

A94

Certificate

100

TLS profile

Post-quantum

RPC reachability

Endpoint identity

URL

https://evm-rpc-story.josephtran.xyz

Host

evm-rpc-story.josephtran.xyz

Chain

Story Testnet

Chain ID

1513

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:43:08.776953339Z

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

Scan reportschema rpcscan-report · captured 2026-10-10T05:52:40.328Z

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.