Click on a language link below and press an edit button if you want to help with translations.
- Afrikaans
- Arabic
- Bengali
- Bulgarian
- Catalan
- Chinese
- Czech
- Danish
- Dutch
- English
- Finnish
- French
- German
- Greek
- Hebrew
- Hindi
- Hungarian
- Italian
- Japanese
- Korean
- Norwegian
- Persian
- Polish
- Portuguese
- Portuguese (Brazil)
- Romanian
- Russian
- Serbian
- Spanish
- Swedish
- Thai
- Turkish
- Ukrainian
- Urdu
- Vietnamese
Feel free to open an issue if you can't find your language or regional dialect.
The data is provided by OpenStreetMap:
Absolutely, you are very welcome to do that. This is a good place to start:
You can delete such places from OpenStreetMap and BTC Map will pick up all your changes within 10 minutes.
OpenStreetMap might have outdated information about some places, you can delete the currency:XBT
tag or set it to no in order to remove this place from BTC Map.
Release APKs are signed by a long-lived release key owned by the BTC Map team. You can verify the signature by checking the certificate's SHA-256 fingerprint:
a63de0923b0c27e3de6ef4e90f3a0d81cca917f9689d2638f1b31949657f1435
The Android SDK build-tools include apksigner:
apksigner verify --print-certs path/to/app.apk
The SHA-256 digest line for Signer #1 certificate should match the
fingerprint above. The certificate subject is O=Team BTC Map.
If you'd rather inspect the certificate from a downloaded APK directly, unzip it
and pass the META-INF signature block to keytool (the exact filename under
META-INF/ varies between builds):
unzip -p app.apk META-INF/*.RSA | keytool -printcert | grep SHA256