Thanks — I’m on this. Short answer up front: MetaMask cannot extract or recover private keys generated by legacy Torus/Web3Auth verifiers. Those keys are derived client-side by Web3Auth/Torus and there’s no MetaMask-side mechanism to reveal them.
What to try next (concise):
- Double-check you’re logging in with the exact same Google account and the same network (mainnet vs testnet).
- Try the legacy Torus interface or torus.js client (if you have any old local session) to export the private key client-side.
- Contact Web3Auth support — they’re the only ones who can confirm whether the legacy xrpl.tor.us verifier or mapping can be restored: What are Embedded Wallets? | MetaMask developer documentation
When you contact Web3Auth, provide these exact details to speed things up:
- Verifier ID: xrpl.tor.us
- Email used to log in (Google account)
- XRPL address: rM8WNndQ1EBeNS2CDGt5nwcdSvwRcbTgLU
- Approximate account creation date and any screenshots or old JWTs/session files
If Web3Auth confirms recovery isn’t possible, the only safe option is to create a new wallet and transfer assets once you have access to the new private key/seed.
I’ve flagged this for the team to review — someone from support will follow up if we need anything else or can help escalate with Web3Auth.
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 monthly Office Hours to discuss this with our engineering team. MetaMask Developer Office Hours