Hi there, if I switch to custom verifiers for social logins will my users have to create new accounts with new wallet addresses or will their keypair remain consistent as it’s tied to their social account?
We would like to launch with the basic tier and then upgrade after a successful trial run but I wanted to check this first.
Thanks.
Hello @adammchambers , welcome to the community.
If you want to use various social login verifiers, and want to get same result (same account),
you need to use Aggregate verifier.
Please refer to this documentation.
Note that you need to be a paid customer if you want to use aggregate verifier on sapphire mainnet.
Hi @pepper, thanks for your response. That’s not quite what I meant though. We dont want to get the same account across various social logins. I just want to confirm that our customers wont lose their accounts if we start with the basic web3auth tier and the default social providers and then upgrade and switch to our own social account verifiers at a later stage.
Referring to this specifically: https://web3auth.io/docs/pnp/going-live#2-create-a-web3auth-production-verifier
For example, will a user retain the same account / wallet if they sign up with google while we are using the default social providers and then we switch to our own google account / api creds at a later stage?
Hello @adammchambers , I got the point.
If you change your verifier then the result account will also be changed.
So if you want to use your own verifier later but keep your user’s account unchanged,
the only way to do that is to pay to create a verifier from scratch.
or there’s another way, to use default verifier from the scratch.
The advantage is that you don’t have to pay up front.
So, the point is that the verifier should never change to get the same account back.
Thanks
