BTC Map
- Name: BTC Map
- URL: https://btcmap.org/
- Category: Bitcoin merchant-acceptance directory / verification and sync infrastructure
- Tags: bitcoin-ecosystem
- Summary: BTC Map is merchant-directory operations, not a payment rail. The real product is merchant tagging, verification, sync, and distribution on top of OpenStreetMap.
- What it does:
- Displays Bitcoin-accepting merchants and communities through a web app, installable PWA, and native mobile apps
- Uses OpenStreetMap tags and community verification flows to maintain structured merchant-acceptance data
- Provides a public wiki for merchant tagging, verification, community administration, onboarding, and support workflows
- Exposes an API stack with a read-oriented REST interface for client apps and a more administrative RPC surface for coordinated write tasks
- Publishes recurring project/blog updates with growth metrics, contributor activity, and product/infrastructure changes
- Maintains separate public repos for the API, web app, Android app, iOS app, and broader project coordination
- Key claims:
- The homepage says BTC Map uses OpenStreetMap to tag places that accept bitcoin and that both the apps and underlying data are free and open-source
- The wiki says it contains detailed content for tagging merchants, onboarding merchants, and using the project’s APIs
- The API overview explicitly separates a read-only REST API from a read/write RPC API, which shows BTC Map is operating a real data-maintenance stack rather than only rendering static map tiles
- The API docs say the REST API is used by all BTC Map client apps and supports incremental sync, which is a meaningful infrastructure clue
- The web-app repo README says the site is a progressive web app and documents how to embed the BTC Map web map into other websites or applications
- The March 2026 update reports 25,181 Bitcoin-accepting places and 650+ communities while also describing major web, Android, and API work, reinforcing that BTC Map is an actively operated data and distribution platform
- Whitepaper: No canonical BTC Map whitepaper or litepaper surfaced in this pass. The clearest primary sources are the official homepage, project wiki, API docs/repositories, web-app repository, and first-party monthly update posts; see
../whitepapers/btc-map-primary-sources-2026-05-01.md. - Sources:
- https://btcmap.org/
- https://gitea.btcmap.org/teambtcmap/btcmap-general/wiki
- https://gitea.btcmap.org/teambtcmap/btcmap-general/wiki/API-Overview
- https://raw.githubusercontent.com/teambtcmap/btcmap-api/master/README.md
- https://raw.githubusercontent.com/teambtcmap/btcmap-api/master/docs/README.md
- https://raw.githubusercontent.com/teambtcmap/btcmap.org/master/README.md
- https://blog.btcmap.org/posts/2026-03/
Internal linkages
- Best upward comparison points for merchant-acceptance and operator-stack context: btcpay-server and blink.
Control surface
-
Power sits in tagging standards, verification policy, sync cadence, community-admin workflows, and which merchants or regions are kept visible enough to feel real.
-
This is map maintenance with public distribution, not a checkout stack.
-
Last reviewed: 2026-06-04 UTC