When there is more than one service using the following Torus Wallet embedding, will the wallet address generated be a different address when the wallet is generated using the same email address or Google account?
Also, when you select Torus Wallet in WalletConnect to connect to Oppensea or other services, the Torus Wallet dashboard opens, where you would enter the URL of the site you want to connect to.
At this time, if I want to use the address generated by the Torus Wallet embedding function as the address to connect to, can I export the private key from the application using the embedding function and register it in the dashboard so that I can connect to Oppensea etc.?
What I was wondering is how it behaves when there are multiple services that use torus wallet embed and the address is generated using the same Google account when logging in to each service.
I would like to know if the address generated is the same address and if it is different, how to switch from the Torus Wallet dashboard.
Also, is the way to load the address generated by torus wallet’s embed into the Torus Wallet dashboard by exporting the service private key that uses the embed wallet and importing it in the Torus Wallet dashboard?
Regarding address generation, I am aware from the following specifications that if the ‘client id’ issued for each service is different, the generated address will also be different.
If nothing is set for this part, a default value will be generated, which will be the same as the address created from the Torus Wallet dashboard or from a service for which nothing is also set?