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 , B² Network Official posts the lowest RPC latency at 236 ms (p50, 24h) across 2 ranked providers. Source: OpenChainBench, https://openchainbench.com/benchmarks/b2-rpc. Chain ID 223. 2 public endpoints, no key: rpc.bsquared.network, b2-mainnet.drpc.org. Full URLs with their 24h median are listed below.
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
b2: 2 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. B² Network Official leads at 236 ms; the chain-official endpoint measures 236 ms. 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, 2 providers live today, 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.
- Cadence: every 60 seconds per provider, from each of 3 probe regions (us-east Virginia, eu-west Amsterdam, sgp Singapore). Headline p50/p90/p99 aggregate across all 3 regions via Prometheus `avg(quantile_over_time(...))`; per-region breakdowns are first-class on this page via the region tabs.
- Payload: `{"jsonrpc":"2.0","id":<rotating>,"method":"eth_getBlockByNumber","params":["latest",false]}`. Plain HTTP POST, identical for every endpoint, no API key in any request.
- Latency measurement, call-result classification (`ok`, `http_err`, `jsonrpc_err`, `stale`, `timeout`) and the archive-depth audit follow the cluster method documented on [rpc-capabilities](openchainbench.com/benchmarks/rpc-capabilities#methodology); this page is the B² Network-scoped view of the same harness, with the same exclusion rules.
- Chain scope: every query on this page is pinned to `chain="b2"`. Provider coverage today: 2 no-key endpoints (B² Official, dRPC, Thirdweb).
Results: 2 providers ranked by RPC latency (p50, 24h)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | B² Network Official | 236 ms | 382 ms | 458 ms | 99.91% (n=4313) |
| 2 | dRPC | 415 ms | 725 ms | 831 ms | 100.00% (n=4319) |
Public endpoints measured
Chain ID 223, currency BTC. The 2 no-key endpoints answering our probes today, with their current 24h median. Paste one into a wallet or a client as is: no signup, no key. Private providers (API key) are never listed with a URL.
B² Network Officialhttps://rpc.bsquared.network236 ms99.9%
dRPChttps://b2-mainnet.drpc.org415 ms100.0%
Median round-trip and success rate over the last 24 hours across the probe regions; the ranked table above carries p90, p99 and the per-region split.
Declared, but not answering our probes
This endpoint is named in the spec and probed on the same schedule as the rest, and answers too rarely to carry a median. Below 5 % success we leave it out of the table rather than publish a latency drawn from a handful of replies. A provider can serve a browser and refuse a datacenter, so this says what a server deployment would meet, not what the endpoint is capable of.
- Thirdweb
https://223.rpc.thirdweb.com1.2 % success over 24 h
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities