https://beta-rpc-node-http.bool.network

Bool Network Beta Mainnetevm

bool.network· beta-rpc-node-http compare ↔● fastest right now● 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

50d

Session resumed

yes

TLS handshake

26ms

Resumption

16ms

TTFB

661ms

RPC block height

TLS handshake

VersionTLS 1.3

CipherTLS_AES_128_GCM_SHA256

KEX groupX25519MLKEM768

ALPNh2

PQ classPQ hybrid

Handshake26ms

Resumed?yes · 16ms

OCSP stapledno

SCTs presentno

Certificate chain

Subjectbool.network

IssuerWE1

Key typeECDSA-P-256

Chain length3

SANsbool.network, *.bool.network

Not before2026-08-31

Not after2026-11-29

Days to expiry50d

Chain SHA-256f6b9575ef9c84fc4…

Misconfigurations

OCSP stapling not enabled no_ocsp_staple

Grades

Posture

C78

Speed

B84

Certificate

100

TLS profile

Post-quantum

RPC reachability

Endpoint identity

URL

https://beta-rpc-node-http.bool.network

Host

beta-rpc-node-http.bool.network

Chain

Bool Network Beta Mainnet

Chain ID

11100

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-10T08:59:02.32963701Z

History (30 days)

no history

Chain peer ranking

This URL is fastest right now

YES

Fastest p50 latency

Latest block height

Current fastest URL

https://beta-rpc-node-http.bool.network

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

Scan reportschema rpcscan-report · captured 2026-10-10T09:04:18.440Z

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.