Currently, zkLogin generates a different wallet address for each OAuth provider, so this is not a bug. Even if you use the same email, it creates a unique wallet address for each login method. If you still have access to your email, you should be able to access both wallets that were generated.

No, it's not a bug, it's how different applications handle wallet creation. When you log in with Google, Google confirms your identity, but it doesn't provide a universal wallet key. Tusky likely has its own system for creating and linking a Sui wallet to your Google ID within their app. Similarly, the official Sui Wallet (or whichever one you used) generates a different unique wallet tied to your Google ID within its own system. Think of it like using your Google login for both a banking app and an email app – they're distinct services. You can recover your Tusky wallet by logging back into Tusky with Google, and your other Sui wallet by logging back into that specific wallet with Google. They are just separate wallets.

Hmm, that's definitely puzzling and not ideal! It's very unlikely to be a bug in Sui itself. What's probably happening is how Tusky is handling your wallet keys when you log in with Google. Think of it this way: your wallet address comes from a secret key. When you log in with Google, Tusky might be generating a brand new secret key (and thus a brand new wallet address) each time, rather than securely linking your Google account to one specific, persistent secret key that it then re-uses. If Tusky doesn't store your original secret key somewhere and associate it with your Google login, or if it doesn't give you a seed phrase (those 12 or 24 words), then it essentially creates a fresh wallet each time it doesn't recognize a previous one. Unfortunately, if Tusky didn't provide you with a seed phrase or private key for your original wallet, and it's generating new ones, recovering the specific original wallet might be impossible through their platform. This is a common challenge with some apps that offer 'social logins' without robust key management or giving users control of their keys. Always look for a seed phrase or private key to back up!