design/migration

16 lines
1.0 KiB
Plaintext

# Migration requirements
## 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 (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 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