https://rpc.bighive-beets.io/osc

Bighive Mainnetevm

bighive-beets.io· rpc compare ↔

Posture score

Speed score

TLS version

TLS 1.3

Cipher

TLS_AES_128_GCM_SHA256

KEX group

classical

PQ class

Classical only

ALPN

http/1.1

Cert expires in

87d

Session resumed

yes

TLS handshake

203ms

Resumption

183ms

TTFB

969ms

RPC block height

3,076,704

TLS handshake

VersionTLS 1.3

CipherTLS_AES_128_GCM_SHA256

KEX groupclassical

ALPNhttp/1.1

PQ classClassical only

Handshake203ms

Resumed?yes · 183ms

OCSP stapledno

SCTs presentno

Certificate chain

Subjectbighive-beets.io

IssuerYE1

Key typeECDSA-P-256

Chain length4

SANsapi.bighive-beets.io, bdbs.bighive-beets.io, bighive-beets.io +3

Not before2026-10-05

Not after2027-01-03

Days to expiry87d

Chain SHA-256d2932553b0413863…

Misconfigurations

OCSP stapling not enabled no_ocsp_staple

Grades

Posture

B83

Speed

D68

Certificate

100

TLS profile

Post-quantum

RPC reachability

100

Endpoint identity

URL

https://rpc.bighive-beets.io/osc

Host

rpc.bighive-beets.io

Chain

Bighive Mainnet

Chain ID

1062

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_128_GCM_SHA256

Last seen

2026-10-07T23:58:03.736017996Z

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

Scan reportschema rpcscan-report · captured 2026-10-10T05:58:59.952Z

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.