Discrepancy in Wallet Addresses Between Web3Auth Provider and Wallet Services Plugin

Help - Plug n Play PnP Web SDKs
1

I am experiencing an issue where the wallet address returned by the Web3Auth provider differs from the address retrieved through the Wallet Services Plugin. The project is a slightly modified version of the Web3Auth Plug-and-Play (PnP) Modal SDK Next.js Quick Start Code . Below is a detailed description of the problem:

Setup :

Using Web3Auth Modal with the WalletServicesPlugin.

Chain: Polygon Amoy Testnet.

Code is based on the official Web3Auth PnP Next.js Quick Start, with minor customizations.

Deployed links:

GitLab Repo : Friday Ameh Matthew / Web3auth Nextjs Project · GitLab

App URL : https://web3auth-nextjs-project.vercel.app

Issue :

The wallet address retrieved via the Web3Auth provider returns Address A.

The address fetched using the Wallet Services Plugin returns Address B.

Both addresses are consistent within their respective contexts but differ from each other.

Troubleshooting Attempts :

Verified both the Web3Auth provider and Wallet Services Plugin are configured for the same chain (Polygon Amoy Testnet).

Ensured the Web3Auth provider is initialized only once to maintain a consistent session.

Cleared Web3Auth’s cache, reauthenticated, and rechecked the addresses.

Request for Help :

Is this a known issue or a bug with the Web3Auth infrastructure?

Could there be a configuration mismatch between the provider and the Wallet Services Plugin?

Any debugging tips or insights would be greatly appreciated.

You can find the full source code in the GitLab repository and test the app via the Vercel deployment link provided above.

Looking forward to your suggestions and guidance!

2

Hi Friday Ameh Matthew! Thanks for reaching out with your detailed description of the issue you’re experiencing. Let’s break down the information for the support team:

Issue Summary:

  • SDK Details: PnP Web SDK
  • SDK Version Number: (Not provided, please specify if you know)
  • Platform: Next.js

Issue Description:

  • Context: Discrepancy in wallet addresses.
  • Chain: Polygon Amoy Testnet.
  • App Setup: Using the Web3Auth Modal with the WalletServicesPlugin.
  • Observed Addresses:
    • Web3Auth provider gives Address A.
    • Wallet Services Plugin gives Address B.

Troubleshooting Steps Taken:

  • Verified both the provider and plugin are for the same chain.
  • Ensured Web3Auth is initialized only once.
  • Cleared cache, reauthenticated, and rechecked addresses.

Links Provided:

Questions for Support:

  • Is this a known issue or a bug?
  • Could there be a configuration mismatch?
  • Suggestions for debugging?

Additional Information Needed:

If you could provide:

  • Code snippets of Web3Auth initialization and login.
  • Any errors from the browser console if applicable.

This information will help ensure the support team can assist you effectively. We appreciate your patience and look forward to helping you resolve this issue!

Note: This response was generated by an AI bot and may require further verification. The Web3Auth support team has tracked this issue and will be responding as soon as possible.

3

Hey @fridayamehmatthew I checked the code, you are using the account abstraction provider. When you use AccountAbstractionProvider, the address that is return is of the smart account address.

Web3Auth Wallet Services as of now doesn’t support Account Abstraction, hence it shows the EOA address. That’s the reason why there’s a discrepancy in the addresses.

4

Thanks for the prompt response

5

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