-
Notifications
You must be signed in to change notification settings - Fork 987
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clean keycard and remove multi-account #9229
Comments
If user forgets Pairing code, PUK and/or PIN, it should be able to reset? |
given the low value ($) of the card it self we've not designed it this way ... If we implement #9064 after v1, the user will be able to recover any keycard if he has his seed (and if PUK/Pairing hasn't been changed form the derived version of the seed by another app...) |
Keycard's side of this task is already implemented, so we need to make sure that there is an API for multiacc removal. |
Ok
Decided with @Rachel Hamlin <[email protected]> that resetting a keycard and
removing its account is post v1.0
Le lun. 11 nov. 2019 à 07:40, Roman Volosovskyi <[email protected]>
a écrit :
… Keycard's side of it is already implemented
<https://github.com/status-im/status-react/blob/develop/src/status_im/ui/screens/hardwallet/settings/views.cljs#L127>,
so we need to make sure that there is an API for multiacc removal.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#9229>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACXOGPLSCAPRS6RAHNAXWCTQTD46VANCNFSM4JBNOV5A>
.
|
DeleteAccount method is added, it deletes account from multiaccounts database and also removes account's DB file. The method is needed for keycard reseting functionality. status-im/status-mobile#9229
DeleteAccount method is added, it deletes account from multiaccounts database and also removes account's DB file. The method is needed for keycard reseting functionality. status-im/status-mobile#9229
DeleteAccount method is added, it deletes account from multiaccounts database and also removes account's DB file. The method is needed for keycard reseting functionality. status-im/status-mobile#9229
@errorists @hesterbruikman could you please have a look at the UI for this? |
would be great to progress on this |
Wondering if this could be captured under 'Delete my profile' for consistency with regular multiaccounts. Result would be more or less this: |
fully agree with you @hesterbruikman |
So this issue #9229 is flow 6 of this figma design https://www.figma.com/file/dEIljL7UPbXgsZUA0Q4qlE5E/Onboarding?node-id=8197%3A858 |
Situation
Currently, after a keycard has been set-up after onboarding the keycard has
Problem
There is no possibility for the user to remove the secrets loaded physically from the card
A user might want to delete the secrets from his card because
Solution
A simple approach would be
"You're about to delete the keys on this card, your pairing code/PUK & PIN remain will unchanged.
You must have your seed if you want to recover any funds from this key in the future. You can now restore another key on this card. Your Pairing code remains unchanged and will be needed if you use a new phone.
Are you sure you want to proceed ? yes/no"
- we leaves PIN, PUK, Pairing uncode untouched on the card
- the secret on the card is deleted
- the multiaccount is removed from the phone
The text was updated successfully, but these errors were encountered: