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
If the user is simply copying and pasting their seed phrase in the the recover wallet edit fields, there's is no error or notification or recognition that there are 24 words being pasted from the clipboard when the seed phrase screen is set to 12 words. Therefore the user can blindly and easily recover a completely different wallet from the first 12 words rather than the wallet they want to recover.
The wallet setup accepts a 24 word paste into a 12 word dialog without any complaints
How it should behave?
The dialog should automatically expand to 24 words and we see all 24 words in the dialog. It has been indicated on slack that this is in development but just to be sure and to follow up afterwards, and to retest, I'm creating this bug.
What os are you seeing the problem on?
Mac/Apple Desktop
What browser?
None
What is your browser version?
Version 122.0.6261.112 (Official Build) (x86_64)
The text was updated successfully, but these errors were encountered:
What version of Wallet are you using?
Version: 0.15.2 (next version)
What is happening?
If the user is simply copying and pasting their seed phrase in the the recover wallet edit fields, there's is no error or notification or recognition that there are 24 words being pasted from the clipboard when the seed phrase screen is set to 12 words. Therefore the user can blindly and easily recover a completely different wallet from the first 12 words rather than the wallet they want to recover.
steps to reproduce
Install Chrome wallet from https://next-wallet.fuel.network/docs/install/
Paste in the 24 words
The wallet setup accepts a 24 word paste into a 12 word dialog without any complaints
How it should behave?
The dialog should automatically expand to 24 words and we see all 24 words in the dialog. It has been indicated on slack that this is in development but just to be sure and to follow up afterwards, and to retest, I'm creating this bug.
What os are you seeing the problem on?
Mac/Apple Desktop
What browser?
None
What is your browser version?
Version 122.0.6261.112 (Official Build) (x86_64)
The text was updated successfully, but these errors were encountered: