Recovery Phrase - Change the way an user is enforced to securely store it

[DangerCZ]

Description of Problem:

• when user creates a recovery phrase (the apps confirm this by showing "Recovery phrase is configured") and tries to start the daemon, error appears "Please copy and securely store the recovery phrase"
• while some enforcement is very important to prevent catastrophic mistakes leading to loss of coins or data, current solution is unlucky as it's forcing users to click the "copy" button even in cases when users don't want to store their recovery phrase on a computer
• while the error says exactly what is wrong and what to do, we've seen on discord that it's not enough and it leads to confusion

Suggested Solution:

When user generates (or re-generates) the recovery phrase, don't update the seed yet and instead display a confirmation dialog with the following:

• Short explanation of importance of the recovery phrase (loss of it = no one can help you)
• "Copy to clipboard" button (self-explanatory)
• "Show QR code" button (shows QR code with checkbox "I saved my recovery phrase" and "Continue" button)
• Checkbox "I wrote down the recovery phrase"
• "Continue" button that is enabled only if user copied it to clipboard, finished the QR code process or checked the last checkbox.

Feel free to comment on this suggestion and/or improve it. Thank you.

Source of this suggestion is discord if anyone wants to check the conversation/issue that led to it: https://discord.com/channels/809849352516141067/827641215356764210/1422879687486607381

[skunk-ink]

This is good. I have to agree with Vicente though. Letting people copy the seed into memory is not a good idea. All it takes is a little bit of malware on someone's PC and the moment they click copy the malware now has their seed.

As frustrating as it is, forcing people to write down the seed and then fill in the blanks like SiaUI did was a far more secure method.

[DangerCZ]

I agree, the solution that doesn't care HOW users store it, but makes them "test" it by asking them to fill the blanks was a great method. Never heard of any user having issues with that.