AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Low 38 Bitcoin

qml: OpenWalletDialog: load any wallet if password matches

Public commit record

What the developer wrote

Authored by f321x

73/100 · Adequate
qml: OpenWalletDialog: load any wallet if password matches

If the user has wallets with different passwords (non-unified pw) and
enters a password on startup that fails to unlock the recently used
wallet this change will automatically open any other wallet if there
is another wallet that can be unlocked with this password.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit changes the mobile/QML version of Electrum so that, when the app starts and the user's entered password does not unlock the most recently used wallet, the app will automatically try to open any other wallet on the device that can be unlocked with that same password. The goal is to help users who have multiple wallets with different passwords. However, it means a password intended for one wallet may silently open a different wallet, potentially showing balances, transaction history, and addresses the user did not expect. It also adds a stored config flag that remembers whether all wallets previously used the same password.

Recommended action

Treat this as a UX/security trade-off worth reviewing. If adopted, add an explicit prompt such as 'Password does not unlock <wallet>. Open <other-wallet> instead?' before loading a different wallet. Ensure getWalletsUnlockableWithPassword does not leak timing or file-existence information, and consider whether the stored did_use_single_password flag creates a fingerprinting or privacy concern. Review whether the fallback should be disabled when wallets have explicit distinct names or when biometric/keychain unlocking is in use.

Security signals we found

01

Cross-wallet password reuse fallback can open an unintended wallet

02

Silent automatic wallet selection bypasses explicit user choice

03

New persistent config flag records past single-password state

04

Behavior is gated only by startup context and a heuristic config flag

05

No explicit user confirmation before loading a different wallet

Risk score

Why this scored 38/100

Our methodology →
Potential impact 8/30
Exploitability 7/25
Stealth signal 6/15
Affected reach 8/15
Confidence 6/10
Evidence quality 3/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.