This PR introduces a dedicated /migrate-user page to facilitate migration for users with legacy Unlock accounts. It allows users to enter their email address to verify if an account exists and determine the appropriate migration steps.
Key updates include:
Integrating ConnectViaEmail to verify account existence.
For legacy 1.0 accounts, prompting users to authenticate using the legacy password-based flow and import into Privy.
For Unlock 2.0 accounts (Coinbase's wallet as a service), completing the login flow (via email or Google) and subsequently importing into Privy.
Issues
Fixes #14858
Refs #14858
Checklist:
[x] 1 PR, 1 purpose: my Pull Request applies to a single purpose
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have updated the docs to reflect my changes if applicable
[ ] I have added tests (and stories for frontend components) that prove my fix is effective or that my feature works
[x] I have performed a self-review of my own code
[ ] If my code involves visual changes, I am adding applicable screenshots to this thread
Description
This PR introduces a dedicated
/migrate-userpage to facilitate migration for users with legacy Unlock accounts. It allows users to enter their email address to verify if an account exists and determine the appropriate migration steps.Key updates include:
ConnectViaEmailto verify account existence.Issues
Fixes #14858 Refs #14858
Checklist: