§ sources
named, not hidden.
oc globe computes nothing of its own. It is a thin client over public Bitcoin infrastructure — a convenience layer, never the authoritative implementation. Everything it draws is independently reproducible against the network itself.
mempool.space
Read directly from your browser over its public API and websocket — no key, no proxy, no server of ours in the path. Open source (AGPL): self-host it over your own Bitcoin Core node and repoint, and nothing about the picture changes.
mempool.space ↗| layer | what you see | endpoint | refresh |
|---|---|---|---|
| blocks | tip height, the pool that found it, the heartbeat pulse | /v1/blocks + ws | live · on each block |
| mempool | depth, throughput, the orbiting fee field | /mempool + ws | live · ~1s |
| fees | next-block fee rate, the fee-band colouring | /v1/fees + ws | live · ~1s |
| nodes | the glowing markers — node count per country | /v1/lightning/nodes/countries | ~hourly |
| lightning | node / channel / capacity totals | /v1/lightning/statistics/latest | ~daily |
| hashrate | network hashrate, difficulty countdown | /v1/mining/pools/1w | ~per block |
Every overlay names its endpoint, how the number is computed from the response, and the command to reproduce it against your own Bitcoin node. Dispute the method — not the messenger.
mempool.space /v1/lightning/nodes/countriesLightning node count per country. A marker sits at the country centroid — mempool reports counts per country, not a coordinate per node, so this answers “where does the network concentrate”, not “which building”.
GET the endpoint on any mempool.space instance, or self-host it over your own Bitcoin Core + LND.mempool.space /v1/lightning/nodes/rankings/liquidity + /nodes/{pubkey}Top nodes by public channel capacity, placed at the coordinates the node self-reports. Nodes without coordinates (Tor-only) are dropped — never positioned by guess.
Cross-check any hub’s capacity and coordinates on your own LN node (lncli getnodeinfo) or a public explorer.mempool.space /v1/blocksThe winning pool is the coinbase tag mempool.space attributes to each block. Share is over the sampled recent blocks — a live hashrate proxy, not an extrapolated network figure.
bitcoin-cli getblock <hash> 2 → decode the coinbase scriptSig and match the pool’s tag/address.mempool.space /v1/blocks + /v1/difficulty-adjustment + globe /api/bip110-historyA block signals iff (version >> 4) & 1 === 1 (BIP-9 bit 4). Rate = signalling ÷ sampled blocks. 55% (1109/2016) is BIP-110’s early-lock threshold over a retarget period. The countdown’s heights are the BIP’s deployment parameters verbatim — mandatory signaling 961,632–963,647, lock-in by 963,648, activation at max_activation_height 965,664, expiry active_duration (52,416) blocks later. Dates are projections, not consensus: blocks inside this epoch at the epoch’s observed pace (mempool’s adjustedTimeAvg), blocks past the retarget at the 10-minute target, anchored on the tip block’s timestamp. None of this is our opinion — it is the block header and the BIP.
bitcoin-cli getblock <hash> → read `version`; ((version >> 4) & 1) is the signal bit. Tally it yourself over any window. Heights: bip-0110.mediawiki §Deployment.mempool.space /v1/difficulty-adjustmentEpoch progress and the estimated change are derived from block timestamps across the current 2016-block period. Retargeting every 2016 blocks is consensus, not an estimate.
bitcoin-cli getblockchaininfo (→ difficulty, blocks) — or recompute from the period’s timestamps.mempool.space /v1/fees/recommended + /mempoolThe recommended fee ladder (sat/vB) and mempool size. The halo colour is a fixed threshold on the fastest rate; backlog ≈ mempool vsize ÷ ~1M vB per block.
bitcoin-cli estimatesmartfee 1 and getmempoolinfo on your own node.mempool.space /v1/blocks + /mempool + websocketTip height, the block heartbeat, mempool depth and throughput — read live over the public websocket. No key, no proxy, no server of ours in the path.
bitcoin-cli getblockchaininfo and getmempoolinfo, or subscribe to your own mempool.space websocket.§ what globe is not
a viewer, not an oracle.
globe holds no keys, moves no funds, and asks for no account. It mints nothing and allocates no protocol identifiers — it is a read over bitcoin's public network state, in the same posture as oc·btc. If mempool.space disappeared tomorrow the network would be unchanged; only this picture of it would go dark.