Feature Request: Flexible HD Derivation Path & Optional BIP39 Passphrase Support

Feature Requests
1

Hello MetaMask team,

First of all, thank you for MetaMask and for keeping the core wallet logic open source.
I’d like to submit a feature request related to HD key derivation flexibility and user-controlled security options.

  1. Flexible HD Derivation Path at the Account Level

Currently, MetaMask derives accounts using a fixed path pattern (e.g. m/44’/60’/0’/0/index).
While this is sufficient for many users, some advanced users would greatly benefit from the ability to:

  • Specify or customize the derivation path at the account level, not only by incrementing the address index
  • Choose alternative paths such as:
    • m/44’/60’/1’/0/*
    • m/44’/60’/x’/0/*
    • or other BIP44 / custom-purpose paths

This would improve:

  • Cross-wallet interoperability (with hardware wallets, CLI wallets, or custom HD setups)
  • Advanced fund segregation strategies
  • Power-user workflows without breaking compatibility with standard accounts
  1. Optional BIP39 Passphrase (“25th Word”) Support

MetaMask currently supports only the mnemonic seed phrase without an additional passphrase.
Adding optional BIP39 passphrase support would:

  • Provide an additional security layer without changing the mnemonic
  • Protect users against seed exposure or physical compromise
  • Align MetaMask with many hardware wallets and advanced software wallets

Ideally, this could be an advanced/hidden option with clear warnings, to avoid confusing novice users.

I believe both features could coexist with MetaMask’s usability-first philosophy by being placed under advanced settings.

Thank you for considering this request, and for your ongoing work on MetaMask.

2

Hi and thank you very much for sharing this feature request! :grinning_face: :hot_beverage: