[Part2] Migrating users from Torus to Web3Auth implementation with Plug&Play

[t.matsumoto]

It’s the follow up for the topic since it’s closed yesterday…

Migrating users from Torus to Web3Auth implementation with Plug&Play

Hi all, We have implemented Torus in our WebApp and use it to authenticate users and create wallets for them if they sign in with Socials (Google,Twitter, Email etc.). We would like to upgrade our implementation to Web3Auth so that we can make use of all the cool new functionalities. However, users who are currently signing into our app with Torus are receiving a specific wallet address created without a clientID. We assume that once we implement Web3Auth, the same users, using the same email …

I’m facing the same issue that is posted in the thread, that is,

From the user perspective it would otherwise be confusing to come back to our WebApp and now not see their assets in their profile because a new wallet is being generated with Web3Auth than with torus.

@clemens did you figure out what @zhen mentioned with w3a plug-n-play no modal?

A Torus integration does not share the user’s key with the application.
you could do this with w3a plug-n-play no modal perhaps?