Different addresses from the same seed ethers v 6.15 vs Metamask

[MousyCatCopilot]

Ethers Version

6.15

Search Terms

derive address metamask

Describe the Problem

I discovered that using the same seed phrase with Ethers and MetaMask results in different addresses for child nodes. Here’s the code I use to generate multiple child addresses:

createBscDepositAddress(index: number) {
    const { mnemonic, password } = this.configService.get('bsc.wallet') as EnvironmentVariables['bsc']['wallet'];

    const hdNode = ethers.HDNodeWallet.fromPhrase(mnemonic, password);

    const childNode = hdNode.deriveChild(index);

    return childNode.address;
  }

Initially, I thought the discrepancy might be due to the password, which could be acting as additional user-provided entropy. However, I tested it without the password, and it still produced different addresses compared to MetaMask.

Code Snippet

Contract ABI

Errors

Environment

node.js (v12 or newer)

Environment (Other)

No response

[MousyCatCopilot]

I think the issue is with derivation paths. My above function generate paths like:

• m/44'/60'/0'/0/0/0
• m/44'/60'/0'/0/0/1
• m/44'/60'/0'/0/0/2

Too much depth

[MousyCatCopilot]

This can be used as workaround

  createBscDepositAddress(index: number) {
    const { mnemonic } = this.configService.get('bsc.wallet') as EnvironmentVariables['bsc']['wallet'];

    const childNode = ethers.HDNodeWallet.fromPhrase(mnemonic, '', `m/44'/60'/0'/0/${index}`);

    return childNode.address;
  }

[ricmoo]

The password is definitely used as a separate source of entropy.

But there is a function in ethers by provided to match the MetaMask derivation path. Keep in mind there are two standards. To match MetaMask, use ethers.getIndexedAccountPath(account) and to match Ledger, use ethers.getAccountPath(account).

There should be no issue with depth, but you must match a path to get a matching private key.

[ricmoo]

Moving to discussions. :)