Our users encountered an unexpected issue a few days back when enabling 2FA for wallet. Upon login, Web3Auth assigned them a new wallet address, contrary to their previous login sessions. This sudden change raises concerns for our test environment.
Note: Users have used the same login method and credentials. ClientId is the same on our DApp
I urgently need clarification on the following:
Wallet Address Change with 2FA: Why did enabling 2FA lead to a new wallet address?
Compulsion of 2FA Setup: Initially, used to get a setup later option for 2FA, but this time there was no choice. why is that?
Criteria for New Wallet Address: Could you please outline the criteria triggering a new wallet address generation?
Can you please share your Dapp URL to check this behavior?
Which SDK & version are you using?
Which framework are you using?
Can you check the environment for your verifier in your Dashboard has been linked to a project and the web3AuthNetwork parameter in your code to be the same as the environment setup for the project?
Share your entire implementation code
Wallet addresses will not be impacted due to 2FA
This depends on the mfaLevel parameter . If it is set to default: the MFA screen will be presented every third login. More information here
Web3Auth accounts are scoped to applications (clientId). The other reasons are:
Different verifiers being used
Different client ids
Different networks
Different social logins (email passwordless and google is not same)
Torus wallet accounts are different from Web3Auth accounts.
You may refer to the below documentation for any further information: