Reading client adoption
Client names, versions and fork IDs are self-reported during protocol handshakes. They describe the nodes we reached during the window, not all BSC nodes or the software behind every validator. An advertised fork ID is not proof of readiness for a future upgrade.
Clients and sync
Clients
Client versions
Sync state
Fork
Open JSON-RPC: 52 nodes over HTTP, 42 over WebSocket. Bootnodes seen: 6 of 6.
Client shares cover 2,318 identified nodes. Version, provider and fork percentages use their identified subsets, which may have different denominators.
Unusual nodes
Key-rotating fleet
15 IP addresses showed 40,740 different node identities in 24 hours, a new one every few seconds. They are left out of every other count on this page.
Old version, current fork
198 synced nodes on the current fork announce a client version too old to follow it, on 2 networks. Advertised versions and fork IDs can be customized; the actual software is not verified.
More detail
For more information or more detailed statistics, write to qwart279@gmail.com.