You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The new BIP39 pw feature could potentially lead to a loss of funds for new, inexperienced wallet users. Here's a simple example flow that could result in loss of funds:
I'm a new user, and never seen the BIP39 pw box before
I enter my MPW unlock wallet pw believing this is what I'm being asked for, making a typo when I enter the pw (no there's currently no validation on the pw field)
a different wallet is created/accessed due to the addition of the new pw
I send funds to this address
later, in a new session, I try accessing my wallet again by typing the same pw, but this time without the typo
a different wallet is created/accessed and I have no way to recover my funds without guessing what the typo was
The new pw field could also do with an explanation of what it is for, and ideally separation of this new advanced wallet feature from simple wallet access.
The text was updated successfully, but these errors were encountered:
First thing that comes to mind is a obvious way of recognizing the generated account. Maybe a partial of the first address locked into the top navigation bar of MPW.
Another solution is keystore files. Many wallets, like Avalanche, allow to access a wallet via keystore, which would mitigate this issue altogether.
A preemptive caution about typos when using the bip39 password detailing what you've already mentioned. Tis a problem generating a rando wallet and sending your funds to the nether realms.
The new BIP39 pw feature could potentially lead to a loss of funds for new, inexperienced wallet users. Here's a simple example flow that could result in loss of funds:
The new pw field could also do with an explanation of what it is for, and ideally separation of this new advanced wallet feature from simple wallet access.
The text was updated successfully, but these errors were encountered: