How you calculate the addresses?

Help - Plug n Play
1

Hello i am testing the mfa with backup seed phrase and i have a missmatch.

With web3atuh user info i am getting the address:

  • 0x7BCf1E47f78523be6d249647A1a46Beb035bd610

But when i am using the backup seed phrase in metamask or with bip39 algo i got:

  • 0xD8B4D94F9D3a6f12EC043D23FA0FF68a00EFbAD2

as first key

what i am doing wrong ??

2

Thanks for sharing the details, Anibal! I understand you’re seeing a mismatch between the address you get from Web3Auth (“0x7BCf1E47…”) and the address you derive using the backup seed phrase in MetaMask or with a BIP39 algorithm (“0xD8B4D94F…”). Let me summarize and guide you:

Issue Overview

  • Issue: Ethereum addresses do not match when comparing:

    • The one received from Web3Auth user info
    • The one derived from backup seed phrase with MetaMask/BIP39

  • SDK / Integration: Web3Auth Plug n Play

Troubleshooting & Guidance

  1. HD Wallet Path Differences

    • Web3Auth may use a different HD derivation path (e.g., m/44'/60'/0'/0/0) than MetaMask or the tool you use. If the derivation path differs, you will get different addresses from the same seed phrase.
    • Please ensure that the derivation path you use in MetaMask matches the one used by Web3Auth. Check our Backup and Restore documentation for guidance on the correct derivation path.

  2. Web3Auth Derivation Path

    • By default, Web3Auth uses m/44'/60'/0'/0/0 for Ethereum addresses. MetaMask also uses this, but some tools default to m/44'/60'/0'/0 (not including the final 0). Please double-check the path used in your tool.

  3. How Keys Are Calculated

    • Web3Auth generates a private key from the seed phrase and then follows the standard derivation to produce the address. See Web3Auth Key Management for architecture details.

How to Proceed

  • In MetaMask:
    When restoring from your backup seed phrase, advanced options allow you to specify the derivation path. Please set it to m/44'/60'/0'/0/0 and check if the first address matches 0x7BCf1E47f78523be6d249647A1a46Beb035bd610.

  • Manual Derivation:
    If using a custom tool/bip39, please make sure you’re deriving the address at the correct path.

Helpful Resources

If you’ve already double-checked the derivation path and still see a mismatch, please share:

  • The code snippet/tools you used for deriving the address with your seed phrase.
  • Screenshots, if possible, of the derivation path settings.

Let me know if this helps or if you have any follow-up questions!

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.

Additionally, we would recommend you to join our biweekly Office Hours to get this resolved even faster. Web3Auth Developer Office Hours

3

I am using m/44’/60’/0’/0

for testing my seed phare that i got from you it is:

gain awkward blast slender tag feel project million wonder zoo detail pole angle select couch index mouse ivory decrease cost debris rough flat stone

and web3auth user info is showing:

0x7BCf1E47f78523be6d249647A1a46Beb035bd610

but with bip39 using m/44’/60’/0’/0 i got: 0xD8B4D94F9D3a6f12EC043D23FA0FF68a00EFbAD2

pd: your link to backup and restore it is broke

4

Hey @anibal,
The backup seed phrase you received is meant to act as an additional recovery factor only within Web3Auth. It’s needed when, for example, you log in from a new device and you don’t have the original device share available — in such cases, you might be asked to use the backup sent to your email or another factor (like a backup social login, passkey, authenticator app, etc.) to recover your account.

It’s not meant to be imported directly into a standard crypto wallet — its purpose and structure are a bit different from traditional seed phrases.

I’d highly recommend reading more about our SSS (Shamir’s Secret Sharing) and TSS (Threshold Signature Scheme) architectures to get a full understanding of how the key is split and protected.