-
Notifications
You must be signed in to change notification settings - Fork 975
implement ledger recovery keys screen #3350
Comments
Please make sure to document the recovery process as part of the steps for QA. Thanks! |
We talked about this and decided having plain text you can copy/paste(/take a screenshot of) would be suitable for the first iteration. |
imo the 'Save' button should be replaced with a 'Show codes' button. as an advanced user, i don't have a printer or want to save the file to disk, i just want to see the code so i can copy/paste it somewhere safe. |
@bradleyrichter why is this in the 'Advanced' panel instead of the Payments panel? |
@diracdeltas It was there because didn't have this new and improved Payments-specific settings dialog: (includes "later" features so please ignore those for now) |
@jkup - i have the wallet recovery implemented in the server. i will provide an API call to |
@bradleyrichter is all the "Advanced Settings.." has for now the view/print and recover buttons? Is the rest of the dialog empty? Also in your first mockup there are both Backup and Recover buttons but in your second one there is only a View/Print button. Which are we going with? |
@mrose17 claims those settings are a slam-dunk to connect? So if easy, we can do them now. The buttons are from different dialogs. Backup and Recover each have their own 2nd dialog. |
accidentally closed when a supporting ledger change was made! |
Bumping this because it's surely going to slip tonight. @mrose17 @ayumi I have the front end work complete. Is the back end work finished? i.e can I get a user's ledger keys and is there an endpoint I can hit to recover them? Assuming this work is done, can one of you help me with how to go about implementing it in the client? Thanks! |
@jkup could you put up a WIP PR for this? Just want to see how close we are on it. Thanks! |
Will do! |
for advanced users who want to backup their ledger recovery keys
@bradleyrichter has mockups for this
The text was updated successfully, but these errors were encountered: