status-im
/
design
mirror of https://github.com/status-im/design.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Update migration

This commit is contained in:
hesterbruikman 2019-07-04 09:18:10 +02:00 committed by GitHub
parent 22922fe554
commit 0b9100d2ce
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
migration
View File

@ -3,13 +3,13 @@
## UI requirements
1. Inform user about V1 before any actions can be taken (right after splash screen)
2. Give users the option to continue on Beta ('single key')
3. Encourage users to start with 'multi-key' on V1
4. Inform users who create a multi-key that they can still access their existing single key identity and funds.
5. Inform users who create a multi-key that other users will not recognize them
6. Inform users that new features will not be supported on single key identities and that other users may no longer recognize them
7. Support users to transfer their funds from their legacy 'single key' to their V1 'multi-key'
2. Give users the option to continue on Beta (SingleAccount)
3. Encourage users to start with MultiAccount on V1
4. Inform users who create a MultiAccount that they can still access their existing single key identity and funds.
5. Inform users who create a MultiAccount that other users will not recognize them
6. Inform users that new features will not be supported on SingleAccount identities and that other users may no longer recognize them
7. Support users to transfer their funds from their legacy SingleAccount to their V1 MultiAccount
8. When user A sends a transaction to a contact in chat, ask user A to verify that the address belongs to them
9. Offer an easy way for users to select a 'multi-key' account on the same device to transfer their funds to
10. Inform users who recover an account that they are provided with a Chat key and name
9. Offer an easy way for users to select a MultiAccount on the same device to transfer their funds to
10. Inform users who recover an account that they are provided with a new Chat key and name
11. Inform users to Register or Connect an existing ENS name to use it with their multikey