Automated spending

Feature Requests
1

Continuing the discussion from MetaMask Developer Office Hours:

1 Like
2

I have now confirmed an important detail about this legacy wallet.

The address I need to recover is:

0xc885eE10E80F4F33DFDe93792b09AadCd646261c

My legacy Torus login was Passwordless Email, NOT Google OAuth.

On the old Torus wallet, I would manually enter my Gmail email address and authenticate through the passwordless email flow. That login produced the wallet address above.

Using Google OAuth / Continue with Google with the exact same Gmail address produces a DIFFERENT wallet, which I understand is expected because Passwordless Email and Google OAuth can use different verifiers.

The old authentication flow now fails because the legacy Web3Auth/Torus integration reports Unsupported Version.

I still have full access to the original email account.

I am not asking MetaMask to recover a seed phrase or private key.

I need help determining the legacy Torus Passwordless Email verifier configuration that generated this address.

Can someone from the Embedded Wallets/Web3Auth team please determine:

  1. What verifier/verifier ID was used by the legacy app.tor.us Passwordless Email login?
  2. Whether that legacy verifier is still operational on the Torus Network.
  3. Whether there is a current authentication endpoint/interface that allows an existing user to authenticate against that same legacy passwordless verifier.
  4. Whether the legacy verifier mapping can be migrated to wallet.web3auth.io.
  5. If the verifier is still operational but the UI has been removed, what supported method exists for a legacy user to authenticate and export their private key?

Please escalate this to someone familiar with legacy Torus verifier configurations rather than treating it as a MetaMask seed-phrase recovery issue.

I can prove control of the original email account and provide historical screenshots/information as necessary. I will not provide a seed phrase or private key.