[Archive] Upgrading sdk to 6.2.1 changes my public / private key from auth

Embedded Wallets (Web3Auth)
1

:classical_building: Archived Content from Web3Auth Community

This topic was originally posted by travis.skweres on 7/10/2023.
This content has been migrated from our previous community forum to preserve valuable discussions.

I’m currently running on an older version:

"@web3auth/single-factor-auth": "^5.1.1",

if I upgrade to “@web3auth/single-factor-auth”: “^6.2.1”

suddenly my authentication returns a different public / private key pair

Is there a way to upgrade the SDK but allow my users to keep their same wallets?

2

@travis.skweres Thanks for reaching out.

Your request has been forwaded to our team and we will get back with further updates at the earliest.

3

Could you please share your Web3Auth initialization and login code snippet?

Please take a look at this thread Web3Auth PnP Web v6 is here with exciting updates! and apply the settings.

4

When I upgrade to 6.2.1, i followed the docs here:

I updated my code to match, something like:

const provider = new EthereumPrivateKeyProvider({
  config: {
    chainConfig: {
      chainId: "0x1",
      rpcTarget: `https://rpc.ankr.com/eth`,
      displayName: "ropsten",
      blockExplorer: "https://ropsten.etherscan.io/",
      ticker: "ETH",
      tickerName: "Ethereum",
    },
  },
});

const web3auth = new Web3Auth({

clientId: “WEB3AUTH_CLIENT_ID”, // Get your Client ID from Web3Auth Dashboard

// Available networks are “testnet”, “mainnet”, “cyan”, “aqua”, .

web3AuthNetwork: “cyan”,

});


web3auth.init({ provider });

However, doing this changed my public / private key pair.

When I downgraded back to 5.1.1, and put my code back to where .init() is empty, and not using the EthereumPrivateKeyProvider, I was returned my expected public / private key(s)

5

Ok, our team are checking on this to replicate your issue and we will get back with further updates.

6

Let me know if you guys have figured out anything

7

@travis.skweres I was able to check this with our team but we were unable to replicate the issue. Can you confirm the following?:

  • Did you change the network?
  • Did you change the verifier details?
  • Did you change the JWT token, for verifierId?

Also, please share the full login and init code.

You can refer to this repo https://github.com/Web3Auth/web3auth-core-kit-examples/tree/main/single-factor-auth-web/sfa-react-example to test with your Verifier details.

8

@travis.skweres Are you still facing any issues? Do you need any assistance?

Do join our upcoming community call - Web3Auth Community Call #4 · Zoom · Luma