Walletwasabi: Generating wallets without confirming to have written the recovery words and password

[yahiheb]

• Go to generate Wallet
• Fill the necessary fields
• Click on Generate

A wallet is generated and you get a notification for that even if you don't confirm that you wrote down the recovery words, this can lead to users using those wallets.
A wallet shouldn't be generated if the user doesn't confirm the he wrote the recovery words and password.

[molnard]

I saw this too. Also, another problem is that the wallet file generated also.

[yahiheb]

Also, another problem is that the wallet file generated also.

This is exactly what I reported, if the wallet file was not generated then it is just a notification problem, but currently it is worse because users can use that wallet by mistake.

[lontivero]

This works as designed. Wasabi display the recovery words in order to allow the user to write them but it is not the wallet duty to make sure the user have written them.

Almost two years ago I made the same suggestion to @nopara73 simply because that's how all the rest of the wallets behave (https://github.com/zkSNACKs/WalletWasabi/issues/1128). However after thinking just a bit about it I totally agree that we shouldn't treat our users as low-IQ people.

In summary, we can always reevaluate our decisions but this is definitively not a bug. I will re-tag it.

[nopara73]

ACK, it's unproductive to discuss over and over old decisions.

[yahiheb]

@lontivero @nopara73 I get what you are saying, and I am not asking to change the generation process.
The only thing that I can suggest is to generate the wallet file only after the user confirms that he has written the recovery words.

Replace the Generate with Next, and generate the wallet file after the user clicks I wrote down my Recovery Words.
So now if the user clicks Next but then stops and doesn't confirm we don't generate a wallet file.

[nopara73]

ACK, sounds like a better workflow.

[MaxHillebrand]

The generation process works as designed, but I agree that the workflow should be changed as you suggest.

But this is not a bug, so it is 0 points.