Getting the different wallet address on different applications. #456
KetulCodiste
announced in
Help
Replies: 1 comment 2 replies
-
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:-
|
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
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.
Beta Was this translation helpful? Give feedback.
All reactions