Same ClientID - different networks generate different wallet addresses, any solution?

Help - Plug n Play
1

Currently, I have some projects using the following dependencies:

  • @web3auth/base": "^6.1.1
  • @web3auth/ethereum-provider": “^6.1.1”
  • @web3auth/modal": "^6.1.1
  • @web3auth/openlogin-adapter": “^6.1.1”

Inside the web3auth Instance (from @web3auth/modal), I set the network to ‘mainnet’, and there are several users (wallet addresses) already using that network. Now, I want to switch my network to ‘cyan’ or ‘aqua’, but when I tried to login using openlogin (using the same Google account), it generates a new address.

Is there any solution for migrating to the new network while keeping the generated address the same?

Note: the web3auth config file followed the official documentary (https://github.com/Web3Auth/web3auth-wagmi-connector/blob/master/demos/rainbowkit-modal-with-plugin/src/RainbowWeb3authConnector.js), exactly as it is.

1 Like
2

@dev2 Hi, different networks will generate different wallet addresses since the nodes are different for different networks.

3

Hi Maharshi, thanks for prompt reply.

we would like to ask the solutions for our problem where we are already live on Mainnet for few months and since last month we hit >10k MAU, our user sometimes experiencing error while login. They saw network congested mostly and slow internet connection (yet their internet is not so bad).

How can we improve this since changing to Aqua is not possible (wallet will changed too)
image

Thank you

1 Like
4

Hi guys, would like to follow up this question. How do we scale up?

  • our users is above 10k MAU right now
  • If we change the network, users wallet (private and public key) will be changed

any solutions? Thank you

1 Like
5

Hey @dev2, sorry for the delayed response. We are conducting migrations on weekends to ensure minimum downtimes. You will have to do no changes, mainnet will be migrated to sapphire mainnet network with increased performance. Please keep checking out the announcements section for more updates on this. Will take some time but you’ll have to just wait for the migrations to complete.

1 Like
6

Got it, thank you for your fast response.
Looking forward to it!

1 Like
7

Hi guys, any update for the migration completion?

1 Like
8

The first phase of the migration has been done, we’re still working on the second phase. We’ll be updating everyone once the second phase is in progress. The downtime expectations will be updated as well once we are moving forward with the second phase of migrations.

9

Hi @dev2, here’s the announcement.

10

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.