2018-04-23 14:54:36 +00:00
|
|
|
---
|
|
|
|
id: 142-recovery-compatibility
|
|
|
|
title: Wallet Recovery Compatibility
|
2018-05-04 04:38:35 +00:00
|
|
|
status: Limbo
|
2018-04-23 14:54:36 +00:00
|
|
|
created: 2018-04-04
|
|
|
|
category: core
|
|
|
|
lead-contributor: pilu
|
|
|
|
contributors:
|
|
|
|
- pilu
|
|
|
|
- antdanchenko
|
|
|
|
- asemiankevich
|
|
|
|
- flexsurfer
|
|
|
|
- chadyj
|
|
|
|
- jpbowen
|
|
|
|
exit-criteria: yes
|
|
|
|
success-metrics: yes
|
|
|
|
clear-roles: yes
|
|
|
|
future-iterations: yes
|
|
|
|
roles-needed:
|
|
|
|
---
|
|
|
|
|
|
|
|
## Meta
|
2018-04-04 22:10:19 +00:00
|
|
|
|
|
|
|
Idea: #142
|
|
|
|
Title: Wallet Recovery Compatibility
|
|
|
|
Status: Draft
|
|
|
|
Created: 2018-04-04
|
|
|
|
Requires (*optional): #94 Wallet Compatibility
|
|
|
|
Replaces (*optional): <Idea number(s)>
|
|
|
|
|
|
|
|
## Summary
|
|
|
|
|
|
|
|
A user should be able to recover accounts created in MyCrypto, MetaMask, Toshi, Cipher Browser, and other
|
2018-04-09 14:02:52 +00:00
|
|
|
mnemonic wallets, into Status.
|
2018-04-04 22:10:19 +00:00
|
|
|
|
|
|
|
## Swarm Participants
|
|
|
|
|
|
|
|
- Lead Contributor: @pilu
|
2018-04-09 14:02:52 +00:00
|
|
|
- Testing & Evaluation: @antdanchenko
|
|
|
|
- Testing & Evaluation: @asemiankevich
|
2018-04-09 14:05:17 +00:00
|
|
|
- Contributor: @flexsurfer
|
2018-04-04 22:10:19 +00:00
|
|
|
- Contributor: <!-- @username -->
|
2018-04-09 14:02:52 +00:00
|
|
|
- PM: @chadyj
|
|
|
|
- UX (if relevant): @jpbowen
|
2018-04-04 22:10:19 +00:00
|
|
|
<!-- - Contributor: @username -->
|
|
|
|
|
|
|
|
## Product Overview
|
|
|
|
|
|
|
|
The wallets named above create the private key with the mnemonic words but without password.
|
|
|
|
|
2018-04-09 14:02:52 +00:00
|
|
|
In those wallets, the password is only used to lock the account and encrypt the private key, and it's not needed to recover it.
|
2018-04-04 22:10:19 +00:00
|
|
|
|
|
|
|
In Status, the same password is used to generate the account and to recover it,
|
|
|
|
so a user cannot recover a wallet created with the 12 words but without password.
|
|
|
|
|
|
|
|
To be compatible with those wallets, we should create and recover wallets without password,
|
|
|
|
and use the passoword only to lock the account on the phone.
|
|
|
|
|
|
|
|
### Product Description
|
|
|
|
|
|
|
|
[need help from UX team]
|
|
|
|
|
|
|
|
### Requirements & Dependencies
|
|
|
|
<!-- Are there bugs or feature requests in other repositories that are part of this Idea? -->
|
|
|
|
<!-- There is no approval unless the idea requires to be reviewed by supporting organelles (Financial, Hiring, or Design). -->
|
|
|
|
<!-- The Swarm must develop a fully fleshed out Requirements document for the idea to proceed, to the satisfaction of participants. -->
|
|
|
|
|
|
|
|
Requires Idea #94 (Wallet Compatibility)
|
2018-04-09 14:16:48 +00:00
|
|
|
Impacts Idea #58-mainnet
|
|
|
|
Impacts Idea #80-onboarding
|
2018-04-04 22:10:19 +00:00
|
|
|
|
|
|
|
### Minimum Viable Product
|
2018-04-09 14:02:52 +00:00
|
|
|
|
|
|
|
Goal Date: 2018-04-20
|
2018-04-04 22:10:19 +00:00
|
|
|
|
|
|
|
Description: <!-- Description of Deliverables-->
|
|
|
|
|
|
|
|
## Dates
|
|
|
|
Goal Date: <!-- Date for evaluation in ISO 8601 (yyyy-mm-dd) format -->
|
|
|
|
|
|
|
|
Description: <!-- Description of Deliverables-->
|
|
|
|
|
|
|
|
Testing Days required: <!-- Days required at the end of development for testing -->
|
|
|
|
|
|
|
|
## Success Metrics
|
|
|
|
<!-- Assuming the idea ships, what would success look like? What are the most important metrics that you would move? -->
|
|
|
|
|
|
|
|
<!-- Example: Onboarding conversion rate. Target >30% full funnel -->
|
|
|
|
|
2018-04-09 14:02:52 +00:00
|
|
|
* 5k daily active users (OKR 2.1 of Q2)
|
|
|
|
* 20% of users send a transaction (OKR 2.4 of Q2)
|
|
|
|
|
2018-04-04 22:10:19 +00:00
|
|
|
## Exit criteria
|
|
|
|
<!-- Launch new onboarding UI flow -->
|
|
|
|
|
|
|
|
Accounts created with the mnemonic wallets named above can be recovered in Status.
|
|
|
|
|
|
|
|
## Supporting Role Communication
|
|
|
|
<!-- Once Requirements and Goals are fleshed out, then it should be communicated to supporting organelles if required -->
|
|
|
|
|
|
|
|
## Copyright
|
|
|
|
Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
|