The mobile app currently forces the user to backup the SRP after importing an account with funds, even though the user does not have any funds in accounts generated from the SRP.
Scenario
GIVEN when a user installs the mobile app and creates a new SRP
AND the user does not have any funds in the account generated from the SRP
THEN the user manually imports an account using a private key
GIVEN the user does not have any funds in account(s) generated from the SRP, and only has funds in the account that was manually imported
THEN the mobile app will force the user to backup the SRP, even though they do not need to do this
Design
n/a
Technical Details
The forced SRP backup flow should only be initiated if the user has funds in SRP-derived accounts
Threat Modeling Framework
No response
Acceptance Criteria
No response
Stakeholder review needed before the work gets merged
[ ] Engineering (needed in most cases)
[ ] Design
[ ] Product
[ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
What is this about?
The mobile app currently forces the user to backup the SRP after importing an account with funds, even though the user does not have any funds in accounts generated from the SRP.
Scenario
Design
n/a
Technical Details
Threat Modeling Framework
No response
Acceptance Criteria
No response
Stakeholder review needed before the work gets merged
References
No response