How it works

The Map,
end to end.

The same privacy posture as the Graph and the Grid — nothing third-party at runtime — applied to a different kind of data. Here is the honest pipeline, including the part the chain can’t give us.

1. 01

   The honest part

   Geography isn’t on the chain

   Bitcoin’s ledger records who and when, never where. A coinbase names a miner’s address, not their country. So unlike the Graph and the Grid — which read the operator’s own node — the Map’s location layer has to come from outside the chain.

2. 02

   Source plane

   Public, cited measurement data

   Network geography is drawn from transparent public sources (mining-pool geolocation indices, reachable-node measurements). Every figure carries its source and as-of date and is presented as an estimate — because that is what it is. The exact sources are being finalised.

3. 03

   Build plane · offline

   Compile a static snapshot

   Those sources are reduced, operator-side, into a small static bundle — a plain file you can inspect, with nothing viewer-specific in it.

4. 04

   Serving plane

   Serve from our own origin

   The bundle is published to storage we control and served from timechainmap.com. No library, font, or asset loads from anyone else.

5. 05

   Serving plane · your browser

   Render locally

   Your browser reads the snapshot and draws the map on your machine. There is no per-view backend call — so there is nothing that could log which country you looked at.