Fastest free B² Network RPC, live no-key endpoint latency
HTTP round-trip latency for eth_getBlockByNumber against every free, no-key public B² Network RPC endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , dRPC leads rpc latency at 359 ms (p50, 24h) on Fastest free B² Network RPC, live no-key endpoint latency. Source: OpenChainBench, https://openchainbench.com/benchmarks/b2-rpc.
Companion page
Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →
B² Network is a Bitcoin L2 combining ZK proof verification with a Rollup+Restaking hybrid model (chain 223), using BTC as the gas token. The official endpoint (`rpc.bsquared.network`) is operated by the B² team, with dRPC and Thirdweb providing additional keyless alternatives probed every 60 seconds from three regions.
Methodology
Per-chain member of the RPC latency cluster, extended to B² Network. We measure the round-trip latency of a single, identical RPC call (`eth_getBlockByNumber`) against every no-key public B² Network endpoint that sustains continuous probing, 3 providers at launch, every 60 seconds, from us-east, eu-west and Singapore. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) so the leaderboard rewards sustained availability rather than fast error messages. The cross-chain view lives on the parent `rpc-capabilities` benchmark; this page is the B² Network-scoped answer with per-region breakdowns as a first-class dimension.
Frequently asked
What is the fastest free B² Network RPC right now?
dRPC currently leads at 359 ms (`eth_getBlockByNumber` p50 over the last 24h), measured against 3 no-key providers probed every 60 seconds from us-east, eu-west and Singapore. The leaderboard re-sorts continuously against fresh Prometheus samples.
Which B² Network RPCs work without an API key?
3 endpoints sustain continuous keyless probing at launch: B² Official, dRPC, Thirdweb. Every listed endpoint was live-verified before inclusion.
Does the fastest B² Network RPC change by region?
Often. The region tabs at the top of the page re-scope every number to a single origin; pick the one closest to where your requests originate.
How is B² Network RPC latency measured here?
One identical JSON-RPC POST (`eth_getBlockByNumber`) every 60 seconds against each provider from each of 3 regions. Responses are classified so an endpoint stuck on an old head or returning errors is never ranked as fastest.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities