Getting the different wallet address on different applications

[Legacy] GitHub Discussions
1

I was going through the documentation of web3Auth. web3Auth have provided the examples for integrating the web3 in different frameworks and blockchains. So I copy-pasted 3 examples in my local machine. 1st one is React js, 2nd one is polygon using react and 3rd one from the demo section of git repo itself(react). In all these demo, whenever I try to connect with the wallet, I am getting the different wallet addresses. For example, if I login with magic link which web3Auth provides in email, then all the 3 demos gives different account address. So for the same email address, I am getting 3 different account addresses in 3 different demos. Likewise, if I login with google, I am facing the same issue here as well. And the wallet address I am getting from google login is different from the wallet address that I am getting through the magic link. So, summarising, for the same email address, I am getting different addresses in different demos, and different addresses for different login mode.



Originally posted by: KetulCodiste

Check the discussion at: https://github.com/orgs/Web3Auth/discussions/456
2

Web3Auth accounts are scoped to applications (clientId). All those demos must be using different clientId and hence you are getting different accounts for same login methods.

You can get your application clientId by registering your project at https://dashboard.web3auth.io.

Other reasons can be:-

  • Different verifiers being used
  • Different client ids
  • Different social logins (email passwordless and google is not same)
  • Torus wallet accounts are different from web3auth accounts.


Originally posted by: himanshuchawla009
3

But That seems very odd !
I have the same Client ID but addresses are still different
Isn’t it one of the main goals of blockchain to check ownership of assets accross different systems ??

Any Work around for this ?