BTC Taro WalletHandbuch
Zum Handbuch

Settings

Settings covers the settings menu, general and privacy options, currency and language, network and Electrum, notifications, storage encryption and biometrics, plausible deniability, tools, feature flags, and About (including self-test, licensing, and release notes).

X-01 Settings menu

Routes: Settings Entry: Home, more icon Tier: Important

Inputs. None. The screen is a list of navigation rows.

Options. Rows, in order:

Behavior. Opens from the home header more icon (and from the wallet asset screen; iOS can also open Settings via the native openSettings event). Android shows an in-page subheader "Settings"; iOS puts the title in the navigation header. Wallet detail rows for Lightning and Multi-Device are disabled when the matching wallet is missing.

Not supported. DefaultView and LightningSettings are registered elsewhere but have no menu entry from this screen.

Depends on. Presence of Lightning and multisig wallets for those rows; LDS DEV API flag for the CHF Taproot row.

Known issues. None recorded. Tests. tests/unit/settings-lightning-wallet.test.js, tests/unit/settings-chf-taproot.test.js, tests/e2e/settings.spec.js (Detox: Currency and Language reached from the menu) Source. screen/settings/settings.js, navigation/WalletsStack.tsx

X-02 General and privacy settings

Routes: GeneralSettings, SettingsPrivacy Entry: Settings, General Tier: Important

Inputs. None beyond the switches and buttons on these screens.

Options.

Behavior. Privacy is reached from General. Biometrics are not on these screens (see Security). Continuity is iOS-only.

Not supported. Biometric unlock/toggle lives under Security, not Privacy.

Depends on. AsyncStorage for preferences; react-native-capture-protection for screenshot blocking; Sentry via analytics when Do Not Track is off.

Known issues. None recorded. Tests. tests/unit/settings-lightning-wallet.test.js, tests/unit/storage-context.test.js, tests/unit/blue-app.test.js Source. screen/settings/GeneralSettings.tsx, screen/settings/SettingsPrivacy.js, blue_modules/Privacy.tsx, blue_modules/clipboard.ts, class/quick-actions.js, blue_modules/WidgetCommunication.ios.js, blue_modules/analytics.js

X-03 Currency

Routes: Currency Entry: Settings, Currency Tier: Important

Inputs. A list of 55 fiat currencies from models/fiatUnits.json, filterable through the native header search bar (matches endPointKey).

Options. Each currency has a price source (CoinGecko 32, CoinDesk 13, Bitstamp 3, Yadio 3, Exir 2, YadioConvert 1, wazirx 1). USD, EUR and GBP use Bitstamp; CHF uses CoinGecko.

Behavior. Default is the saved preference; otherwise the device’s first locale currency when it is in the list, else USD. Selecting a currency fetches a live rate first. On success it persists preferredCurrency, re-inits and refreshes. On failure it shows "There was an error while obtaining the rate for the selected currency." and keeps the previous choice. The footer shows "Price is obtained from" plus the provider name, the rate, and last updated. Rates are refetched at most every 30 minutes and count as stale after 31 minutes or after a fetch error.

Not supported. Custom or user-defined currency codes outside the list.

Depends on. The currency’s configured price provider endpoints.

Known issues. None recorded. Tests. tests/unit/currency.test.js, tests/integration/Currency.test.js, tests/e2e/settings.spec.js (Detox: EUR shows the home balance in euro) Source. screen/settings/currency.js, models/fiatUnits.json, models/fiatUnit.ts, blue_modules/currency.js

X-04 Language

Routes: Language Entry: Settings, Language Tier: Important

Inputs. A list of 46 languages from AvailableLanguages, English first. RTL languages: Arabic, Farsi, Hebrew.

Options. Selecting a language saves it immediately.

Behavior. Default is the saved lang; otherwise the device’s first supported locale, else en. The choice is stored in AsyncStorage lang and applies immediately. Switching into or out of an RTL language shows "Restarting DFX Bitcoin Wallet is required for the language orientation to take effect."

Not supported. Languages outside AvailableLanguages.

Depends on. Locale files under loc/.

Known issues. None recorded. Tests. tests/unit/loc.test.js, tests/e2e/settings.spec.js (Detox: German applies at once and after a restart) Source. screen/settings/language.js, loc/languages.ts, loc/index.ts

X-05 Default view on launch

Routes: DefaultView Entry: Not reachable in the current build Tier: Nice

Inputs. Switch "View All Wallets" (default_wallets), disabled when there are no wallets. When off, a wallet is chosen via SelectWallet.

Options. Stored value key: AsyncStorage ONAPP_LAUNCH_SELECTED_DEFAULT_WALLET_KEY ("View All Wallets" default on).

Behavior. Not reachable in the current build: the route is registered but no navigation entry exists. If reached, the switch controls whether launch opens the wallet list or a selected wallet. At launch, App.js still honours a stored selection and opens WalletTransactions for that wallet when there is no deeplink.

Not supported. Changing this preference from the Settings UI (no entry point).

Depends on. class/on-app-launch.js and the launch path in App.js.

Known issues. None recorded. Tests. None. Source. screen/settings/defaultView.js, class/on-app-launch.js, App.js

X-06 Network and Electrum server

Routes: NetworkSettings, ElectrumSettings Entry: Settings, Network Tier: Important

Inputs. Electrum host (trimmed text), port (number pad), Use SSL switch. Optional QR of host:port:s|t or a bluewallet:setelectrumserver?server= string. Offline Mode switch.

Options.

Behavior. There is no user-facing preset list. The built-in pool is 8 public Electrum servers; the app picks one at random and rotates on failure, and also rotates peers every 30 minutes. A saved custom server replaces the whole pool: every reconnect uses it. If it becomes unreachable, the app retries the same server repeatedly and does not fall back to the built-in pool; balances and history stop updating and Electrum-dependent sends fail. No Tor transport is bundled; whether .onion hosts work on mobile is not verified in code.

Not supported. Lightning (LNDHub) settings row on this screen (removed relative to upstream; that screen is unreachable). Automatic fallback from a bad custom server to the built-in pool.

Depends on. Electrum connectivity (BlueElectrum.js); app-group group.swiss.dfx.bitcoin on iOS for widget mirroring of host/ports.

Known issues. None recorded. Tests. tests/integration/BlueElectrum.test.js, tests/unit/electrumBatchingDetection.test.js, tests/unit/storage-context.test.js Source. screen/settings/NetworkSettings.js, screen/settings/electrumSettings.js, blue_modules/BlueElectrum.js

X-07 Notification settings

Routes: NotificationSettings Entry: Settings, Network, Notifications Tier: Important

Inputs. Push Notifications switch; GroundControl URI field (placeholder = default URI). Hidden debug: tap the footer text nine times to show push token, permissions and stored notifications, with a copy button.

Options. Push Notifications (NotificationsSwitch): on clears the opt-out flag and sets server levels or requests permission; off calls setLevels(false), which stores the don’t-ask flag. Effective state requires not opted out, a device token, and server level_all. Empty GroundControl URI restores the default; save checks ${uri}/ping for a description field ("Saved" / "Invalid URI").

Behavior. Entry appears only when notifications are capable (iOS, or Android with Google or Huawei services). Provider is GroundControl (BlueWallet’s open-source push relay); the default server is BlueWallet’s public GroundControl instance, not a DFX server. The wallet registers on-chain addresses, Lightning payment hashes and txids for paid/confirmed pushes on wallet add, receive/invoice creation, and send/broadcast/CPFP/PSBT flows. Nothing is sent without a push token or when the user chose don’t ask. The OS permission prompt can also be triggered from receive flows. On Android below API 33 a rationale uses "Would you like to receive notifications when you get incoming payments?" / "No, and don’t ask me again".

Not supported. Notifications on Android without Google or Huawei services (no menu row).

Depends on. react-native-notifications (APNs/FCM); GroundControl URI (default from groundControlUri, overridable).

Known issues. None recorded. Tests. tests/integration/notifications.test.js Source. screen/settings/notificationSettings.tsx, blue_modules/notifications.ts, blue_modules/constants.js

X-08 Storage encryption and biometrics

Routes: EncryptStorage Entry: Settings, Security Tier: Critical

Inputs. Biometrics switch "Use {type}" (Face ID / Touch ID / Biometrics), shown only if the device is biometric-capable. Encrypted and Password Protected switch: password and retype when enabling; password when disabling.

Options.

Behavior. Title is "Security". Wallet JSON is encrypted with CryptoJS AES passphrase mode (OpenSSL-style key derivation; no PBKDF2/scrypt found). Storage holds a JSON array of encrypted buckets; flag data_encrypted='1'. Wallet data lives in the platform secure store (key data, accessibility WHEN_UNLOCKED_THIS_DEVICE_ONLY), with a Realm keyvalue.realm fallback copy encrypted by a random key held in the keychain. Settings and flags remain in plain AsyncStorage. At unlock, encrypted storage prompts "Enter password" / "Your storage is encrypted. Password is required to decrypt it." and rejects empty input. Wrong password re-prompts; on iOS after 10 failures, "You have attempted to enter your password 10 times…" can wipe secure-store data, data_encrypted and Biometrics after biometric/passcode confirmation; Android re-prompts indefinitely. Encryption clears quick actions and zeroes the widget balance; those privacy switches are hidden while encrypted. Whether the launch biometric gate fires automatically for unencrypted storage is not verified in code (code reading suggests the mount path skips it). Whether the iOS wipe also removes the Realm fallback copy is not verified in code.

Not supported. Using biometrics to unlock encrypted storage. Password strength rules. A dedicated “reset app” / delete-all-data setting (deletion paths are delete main wallet, iOS wipe after failed passwords, or Clear AsyncStorage for language/currency cache only).

Depends on. Platform secure store / keychain; CryptoJS encryption; react-native-biometrics for gated actions (send confirm, PSBT flows, LNURL-pay, OpenCryptoPay commit, export, xpub, multisig screens, wallet details/delete, and related headers).

Known issues. None recorded. Tests. tests/unit/encryption.test.js, tests/unit/blue-app.test.js, tests/unit/storage.test.js, tests/e2e/encrypted-storage.spec.js (skipped until the Android prompt fix #281 is merged), CF-04 Source. screen/settings/encryptStorage.js, blue_modules/encryption.js, BlueApp.js, class/biometrics.js

X-09 Plausible deniability

Routes: PlausibleDeniability Entry: Settings, Security, while encrypted Tier: Important

Inputs. Button "Create Encrypted Storage"; password and retype for the decoy storage.

Options. Help text explains creating another encrypted storage with a different password so a coerced disclosure unlocks empty “fake” storage while the main storage stays sealed.

Behavior. Shown only while storage is encrypted. Create prompts "Create a password" / "Password for the fake storage should not match the password for your main storage." If the password equals the current one or decrypts any existing bucket: "Password is currently in use. Please try a different password." Retype mismatch: "Passwords do not match. Please try again." On success it appends a new encrypted bucket with empty wallets, switches the running session into that empty storage (fake password cached), refreshes the wallet list, shows "Success" and pops to top. At the next launch, whichever password decrypts a bucket opens that bucket; return to the real wallets by restarting and entering the main password. Several decoys can be created (one bucket each).

Not supported. Listing or deleting decoy buckets in the UI.

Depends on. Encrypted storage (X-08) and the multi-bucket decrypt path in BlueApp.js.

Known issues. None recorded. Tests. tests/unit/blue-app.test.js, tests/e2e/encrypted-storage.spec.js (skipped until the Android prompt fix #281 is merged), CF-04 Source. screen/plausibledeniability.js, BlueApp.js

X-10 Tools

Routes: Tools Entry: Settings, Tools Tier: Nice

Inputs. None on the Tools menu itself; each row opens a separate tool screen owned by the send area.

Options.

Behavior. Header title is "Tools". Self-test and the performance test are not here; they live under About.

Not supported. Running self-test or performance test from Tools.

Depends on. Loaded wallets for address ownership; Electrum for broadcast.

Known issues. None recorded. Tests. None. Source. screen/settings/tools.js

X-11 Feature flags

Routes: FeatureFlags Entry: Settings, Feature Flags Tier: Important

Inputs. Four switches with hardcoded English labels. All flags persist in AsyncStorage as '1'/'' and default off. On a read error all are reset to off.

Options.

Behavior. Always reachable from Settings; screen strings are not localized.

Not supported. Per-environment gating of the Feature Flags menu itself (always visible).

Depends on. AsyncStorage flag load/save; DFX services buttons and wallet details for flag effects; config keys REACT_APP_LDS_URL / REACT_APP_LDS_DEV_URL.

Known issues. None recorded. Tests. tests/unit/settings-chf-taproot.test.js, tests/unit/storage-context.test.js, tests/unit/dfx-services-buttons.test.js Source. screen/settings/FeatureFlags.tsx, blue_modules/storage-context.js, BlueApp.js

X-12 About, self-test, licensing, release notes

Routes: About, Selftest, Licensing, ReleaseNotes Entry: Settings, About Tier: Nice

Inputs. About is mostly static content and navigation. Self-test runs after the user taps "Run self-test" / "Run self-test again" (hardcoded English). Performance test derives up to 1000 bech32 addresses within 10 s. Licensing is static MIT text. Release notes render bundled release-notes.json.

Options. About shows the DFX logo, "The DFX Bitcoin-only Wallet is a softfork from bluewallet.io with an integrated buy and sell option from DFX AG.", "Always backup your keys!", Leave us a review (Android only with Google Play services), Twitter/Telegram/GitHub links, Built with list, Release notes, MIT License, Run self-test, and "Test performance". Footer: app name, version, build and branch, build date, bundle id, window size, device Unique ID (copy as userId:<id>), and "Environment: X" when DFX_ENV is not prd. Licensing is MIT with "Copyright (c) 2018-2023 BlueWallet developers" and title "License" (no third-party dependency list). Release notes come from git log subjects/bodies since the previous tag (raw commit messages, not curated notes).

Behavior. Self-test is blocked when Offline Mode is on ("Self-testing is not available with Electrum Offline Mode. Please disable offline mode and try again."). Nothing runs on open until the user taps Run. A live step log shows ✓/✗ and timings; success shows "OK" plus "All internal tests have passed successfully. The wallet works well." Checks include key generation, Electrum connect/balance for a fixed address, Aezeed, signing, WIF, AES, BIP39/BIP32, HD wallets, scrypt, BIP38, SLIP39, Linking.canOpenURL(https), multisig signing/import/export/cosign paths, and (in __DEV__ only) Electrum history of a historical multisig withdrawal. Android only: "Test Save to Storage" writes/exports a storage save test file. Whether the Detox self-test assertion still matches the button-tap UI is not verified in code.

Not supported. Curated release notes (file lists raw commit messages). Third-party license inventory on the Licensing screen.

Depends on. Network for Electrum-backed self-test steps; Offline Mode must be off; release-notes.json bundled at build time; DFX_ENV for the environment footer line.

Known issues. None recorded. Tests. tests/unit/settings-lightning-wallet.test.js, tests/integration/App.test.js, tests/e2e/onchain.spec.js (Detox: self-test passes) Source. screen/settings/about.js, screen/selftest.js, screen/settings/licensing.js, screen/settings/releasenotes.js