https://api.elastos.io/eid

ELA-DID-Sidechain Mainnetevm

elastos.io· api 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

58d

Session resumed

yes

TLS handshake

157ms

Resumption

60ms

TTFB

1.14s

RPC block height

29,258,403

TLS handshake

VersionTLS 1.3

CipherTLS_AES_128_GCM_SHA256

KEX groupX25519MLKEM768

ALPNh2

PQ classPQ hybrid

Handshake157ms

Resumed?yes · 60ms

OCSP stapledno

SCTs presentno

Certificate chain

Subjectelastos.io

IssuerWE1

Key typeECDSA-P-256

Chain length3

SANselastos.io, *.elastos.io

Not before2026-09-06

Not after2026-12-05

Days to expiry58d

Chain SHA-256f35fdf25b5db1c74…

Misconfigurations

OCSP stapling not enabled no_ocsp_staple

Grades

Posture

A+96

Speed

F59

Certificate

100

TLS profile

Post-quantum

RPC reachability

100

Endpoint identity

URL

https://api.elastos.io/eid

Host

api.elastos.io

Chain

ELA-DID-Sidechain Mainnet

Chain ID

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-07T23:57:33.463387899Z

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

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

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.