Archived Content from Web3Auth Community
This topic was originally posted by mitch1 on 4/15/2025.
This content has been migrated from our previous community forum to preserve valuable discussions.
Let’s assume I have already implemented passwordless email authentication without creating a verifier (the system will use a native verifier). Now I would like to add other login methods like google. First, I had different wallet addresses even though the email was the same on the passwordless email and google methods. Then I found a solution that I need to create a custom aggregate verifier that encompasses the verifier of both login methods (passwordless email and google) so that I can have the same wallet address regardless of the login method chosen. My question is when I log in with the new verifier, will it have a new wallet (knowing that the new verifier is not the same as the old verifier)? If so, how can I migrate the private keys from the old verifier (which was the default) to the new one?