Hello, we have setup Web3Auth plug and play using the default verifiers managed by Web3Auth, if we decide to use custom verifiers, will this affect our current users who have previously signed up while we were using the default verifiers?
Thanks
Hey @benjamin.groves, for the transition to appear seamless for your users, I will suggest you to explore the possibility of creating aggregate verifiers. In this way, you can keep your existing verifier and the new custom verifier as sub-verifiers. Then, the sub-verifiers will always give the same account for your users.
A brief about aggregate verifiers can be found here.
I’ll link a documentation on setting up an aggregate verifier here for your convenience.
Hey @maharshi, I understand what you are suggesting and it seems like a good approach. However, are you suggesting that we can use the Web3Auth Default Verifiers as described here as a sub-verifier in our own custom aggregate verifier?
Thanks.
Hi,
I’d like to chime into this discussion, as we’re currently trying to migrate from the ‘old’ openlogin sdk to the new single factor auth, and i found out that when creating a verifier for custom JWT, i do get a different private key for the same user than using the old auth.
Would using a custom aggregate verifier which only contains a customauth JWT work in this case? so:
i create a new custom aggregate verifier on our mainnet using the firebase JWT like in the example in the docs, and then get the same (existing) private key from the same google account that’s previously signed up using the old auth?
thank you.
Hi @benjamin.groves, I would like to suggest a correction to your understanding of aggregate verifiers. Aggregate verifiers are an umbrella that contains various types of sub-verifiers(sub-verifiers are verifiers that can exist standalone but like for your use case we are deciding to put it under one aggregate verifier so that your users get same wallet addresses, no matter which verifier is being used.)
You can refer to our docs for more info on aggregate verifiers.
For your use case, there can be other solutions as well, but this just was on top of my head. Let me know if this suits you or I can consult the product team if there is some other way we can go about this.
hey @circleslandnow, let me get back to you in a while. I need some more info on the old SDKs. Thank you for your patience. By that time, I’ll advise you to please open up a new thread so that it is easier to focus on your issue and so that you can get personalised attention.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.