https://lb.routeme.sh/rpc/evm/12306

Fibonacci Mainnetevm

routeme.sh· lb 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

52d

Session resumed

yes

TLS handshake

17ms

Resumption

11ms

TTFB

894ms

RPC block height

40,425,905

TLS handshake

VersionTLS 1.3

CipherTLS_AES_128_GCM_SHA256

KEX groupX25519MLKEM768

ALPNh2

PQ classPQ hybrid

Handshake17ms

Resumed?yes · 11ms

OCSP stapledno

SCTs presentno

Certificate chain

Subjectdev.lb.routeme.sh

IssuerWE1

Key typeECDSA-P-256

Chain length3

SANsdev.lb.routeme.sh, lb.routeme.sh

Not before2026-09-02

Not after2026-12-01

Days to expiry52d

Chain SHA-2568e935a298c5d9676…

Misconfigurations

OCSP stapling not enabled no_ocsp_staple

Grades

Posture

A+96

Speed

C74

Certificate

100

TLS profile

Post-quantum

RPC reachability

100

Endpoint identity

URL

https://lb.routeme.sh/rpc/evm/12306

Host

lb.routeme.sh

Chain

Fibonacci Mainnet

Chain ID

12306

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-10T07:39:05.045296311Z

History (30 days)

no history

Chain peer ranking

This URL is fastest right now

Fastest p50 latency

Latest block height

Current fastest URL

https://node7.fibo-rpc.asia

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

Scan reportschema rpcscan-report · captured 2026-10-10T07:41:45.365Z

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.