§ 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 |
§ 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.