[Archive] Upgrading to V7 Leads to New Address

Embedded Wallets (Web3Auth)
1

:classical_building: Archived Content from Web3Auth Community

This topic was originally posted by farrel on 9/13/2023.
This content has been migrated from our previous community forum to preserve valuable discussions.

Hey everyone,

I’ve been using Web3Auth since November 2022 with the Base plan since our monthly active users are currently under 50. Today, I received a notification for the v7 update and saw the new dashboard with the migration to project. I migrated and updated the SDK without changing any configuration, but I received the following error when trying to sign in:

Invalid params, The current subscription plan is Base and requesting feature(s): custom auth are not available on Base plan. Please upgrade to Growth or above plan at https://dashboard.web3auth.io to use these features

I checked the newest documentation and found that we no longer need to provide the adapterSetting and the network. So I tried logging in with Google but the address is now different, turned out it was using a different verifier (now is “web3auth”) and the redirect link is “h ttps://auth.web3auth.io/v5…”.

I understand that a different verifier would lead to a different address, but it would means that my users would lose their wallet if I don’t upgrade to the Growth plan. So is upgrading necessary? or there might be some configurations that I could do to retain my users’ wallet?

2

@farrel Welcome Aboard!

Could you share the documentation you are referring to?

If you need to use Custom Auth, you would need to upgrade to Growth or above.

3

From the quick start page. I had to create a custom verifier when I initially integrated Web3Auth. It’s a bit unfortunate that we might need to upgrade to continue using the verifier.

Do you happen to have any information on when the V6 SDK or the v4 API (I’m assuming) will be sunsetted?

4

Where are you getting information that adaptersetting and network need not be specified?

You can refer to this announcement [IMP!] Web3Auth v5 sunset date

5

I simply concluding from the step 3 to 4 when implementing Google which there are no verifiers involved.

Regarding the announcement, I’d like to clarify for my case I’m using the v6 SDK and the API redirects to “https://app openlogin com/v4…”, so the date will be on 31st December 2023?

6

Ok.

Yes, that is right Web3auth V6/Openlogin V4 will be deprecated on 31st December 2023