wss://evm-rpc-ws.nibiru.fi

Nibiru cataclysm-1evm

nibiru.fi· evm-rpc-ws compare ↔● PQ hybrid

Posture score

Speed score

TLS version

TLS 1.3

Cipher

TLS_AES_256_GCM_SHA384

KEX group

X25519MLKEM768

PQ class

PQ hybrid

ALPN

Cert expires in

87d

Session resumed

TLS handshake

82ms

Resumption

83ms

TTFB

404ms

RPC block height

TLS handshake

VersionTLS 1.3

CipherTLS_AES_256_GCM_SHA384

KEX groupX25519MLKEM768

ALPNh2

PQ classPQ hybrid

Handshake82ms

Resumed?no

OCSP stapledno

SCTs presentno

Certificate chain

Subjectrpc.nibiru.fi

IssuerYR2

Key typeRSA-2048

Chain length3

SANsevm-rpc-ws.nibiru.fi, evm-rpc.nibiru.fi, grpc.nibiru.fi +2

Not before2026-10-07

Not after2027-01-05

Days to expiry87d

Chain SHA-256f93ba7ccf9bcf742…

Misconfigurations

OCSP stapling not enabled no_ocsp_staple

Grades

Posture

C78

Speed

A+95

Certificate

100

TLS profile

Post-quantum

RPC reachability

Endpoint identity

URL

wss://evm-rpc-ws.nibiru.fi

Host

evm-rpc-ws.nibiru.fi

Chain

Nibiru cataclysm-1

Chain ID

6900

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_256_GCM_SHA384

Last seen

2026-10-10T05:08:45.958448254Z

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

Scan reportschema rpcscan-report · captured 2026-10-10T06:01:01.539Z

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.