Hello, I’m looking for assistance with web3auth and to be more specific i’d like to reconstruct a tKey that was previously generated from the Binance Extension Wallet years ago. They deprecated the extension since then and therefore I’d like to reconstruct the key somehow.
I’ve been lead to use the https://tkey.io interface, but the google login credential for the app seems to be outdated:
Thanks — I’m sorry you ran into that. I pulled the key details from your message and a short next-steps plan for the support team so they can act quickly.
Platform: web / browser (inferred from screenshot)
What that error means (short)
The Google OAuth client configured for the tKey app is sending a redirect URI that doesn’t match the list of authorized redirect URIs in the Google Cloud Console for that OAuth client. This is a server/app configuration problem on the tKey/Web3Auth side — there’s nothing you can fix from your browser if the app’s OAuth client is misconfigured.
Suggested next steps (ordered)
Try alternative login methods on tkey.io (if available) — e.g., other social providers — in case you can get in without Google.
Contact the tKey / Web3Auth maintainers/support and include the exact error + your screenshot. This is something they must fix by updating the OAuth client’s authorized redirect URIs. Useful places to contact:
Web3Auth GitHub (issues) or their Discord/community channels (search “Web3Auth Discord”)
If you still have the old Binance Extension wallet data (browser profile or an exported backup), recovery may be possible by extracting the extension’s stored data or using any private-key/seed backup you exported earlier. If you want, I can guide you through extracting extension storage from your browser profile.
If you don’t have other login providers or extension data, ask Web3Auth/tKey to help with an account-recovery path (they may need to rotate the OAuth config or expose an alternate recovery flow).
Info to include when you contact tKey/Web3Auth (this will speed up triage)
Browser + OS (please tell me which you used so I can add it here)
Whether you originally created the tKey via the Binance Extension Wallet and whether you still have that extension’s profile files/backups
Do you want me to:
Draft a short message you can paste to Web3Auth/tKey support with the above details?
Walk you through extracting the old extension data (if you still have the browser profile) to try a manual recovery?
I can help prepare the support message — if yes, please confirm which browser & OS you used and whether you still have the old extension files or any exported backup.
Note: This response was generated by an AI bot and may require further verification. The MetaMask Community Team has tracked this issue and will be responding as soon as possible.
Additionally, we would recommend you to join our biweekly Office Hours to get this resolved even faster. MetaMask Developer Office Hours
I have, they told me to reach out to Torus and related tKey personnel. I no longer have the device key, which means the only way I can recover my seedphrase is via the Google Login and the password. It seems to me like maintaining the google login is a mandatory requirement for the tKey liability and responsability towards users. Is there a reason that prevents you from updating the google credentials ?
You can try logging in on https://accounts.web3auth.io and check if that helps you. If not then your particular account is linked to the google credentials of Binance and not Torus/ Web3Auth. We can help you construct the key only if we get the Google ID Token.
