Skip to content
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

Implement add account with recovery phrase flow #4302

Closed
Tracked by #4035
soroushm opened this issue May 12, 2022 · 0 comments · Fixed by #4329
Closed
Tracked by #4035

Implement add account with recovery phrase flow #4302

soroushm opened this issue May 12, 2022 · 0 comments · Fixed by #4329

Comments

@soroushm
Copy link
Contributor

soroushm commented May 12, 2022

Description

User will enter the recovery phrase then setup a password for encryption then user can download the backup json schema

Acceptance Criteria

  • design
  • Allow user to enter the recovery phrase
  • Allow user to select the new password for encryption
  • Allow user to download encrypted backup json schema
  • Its need to Check the account is already added
  • At the end redirect user to the dashboard
  • Set current user to store
  • Add e2e test to make sure flow working fine

Additional Information

  • It need to use a multiStep and reuse the component from tickets:
@soroushm soroushm changed the title Implement add account with passphrase flow Implement add account with recovery phrase flow May 17, 2022
@sridharmeganathan sridharmeganathan added this to the Sprint 75 milestone May 24, 2022
@ManuGowda ManuGowda moved this from Backlog to In Progress in Lisk Desktop Version 3.0.0 May 30, 2022
eniolam1000752 added a commit that referenced this issue Jun 3, 2022
…recovery-phrase-flow

Implement add account with recovery phrase flow - Closes #4302
Repository owner moved this from In Progress to Done in Lisk Desktop Version 3.0.0 Jun 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

3 participants