shapeshift
Handle factory-new KeepKey connections
Overview
Upon connecting a factory-new KK -- or one which has been recovered after a failed firmware update -- the user gets dropped to this screen, which could be misleading if the user didn't initiate a wipe.
References and additional details
Currently, when we receive a NOTINITIALIZED event from a KeepKey, we dispatch the OPEN_KEEPKEY_INITIALIZE action (assuming the user wiped it).
This even it also emitted when connecting a factory-new KeepKey. We'll need a way to distinguish between a factory-new KeepKey that has not been initialized, and a KeepKey that has been wiped and needs to be re-initialized.
Acceptance Criteria
https://github.com/shapeshift/web/issues/1609#issuecomment-1112649156
Need By Date
No response
Screenshots/Mockups
No response
Estimated effort
No response
Lets update the title of this modal to "Get Started with KeepKey". Update the rest of the copy to "Your KeepKey is set to factory default settings. Create a new wallet, or restore a wallet using your secret recovery phrase" As this is the first modal in this flow lets also remove the back button. Also, the close button should redirect user back to the connect wallet
recap:
- update title to "Get Started with KeepKey"
- update copy to "Your KeepKey is set to factory default settings. Create a new wallet, or restore a wallet using your secret recovery phrase"
- remove back button
- closing out (x) redirects to connect wallet
