Configurable derivation path for custom RPCs

Feature Requests
1

What

  • MetaMask uses m/44'/60'/0'/0 as the derivation path (BIP44),
    and this value is hardcoded to be the same for all networks.
  • I would like to be able to set a custom value for the derivation path,
    especially when configuring a custom network.
2

Why

  • This is important because MetaMask is used on other networks (including RSK),
    and these may use different derivation paths.
    • The MetaMask already uses derivation path conforming to the BIP39 and BIP44 standards;
      and its custom network configuration screen already supports specifying different chainIds…
      so it would make sense to allow for custom derivations paths as defined in SLIP0044
      (Registered coin types for BIP44)
  • This is also important for Ethereum users who originally set up their wallets
3 Likes
3

Refs

  • BIP39, BIP44, SLIP44

(Would add hyperlinks, but new user restrictions! also had to split this post up for some reason)

3 Likes
4
2 Likes
5

Just signalling my support for this. Being able to customise the derivation path when importing a hardware wallet would be super duper helpful!

2 Likes
6

Thanks the request! This looks like an interesting submission!

We will be sure to look into this and discuss the feasibility.

2 Likes
7

There’s still demand for this in the RSK community:

research.rsk.dev/t/metamask-derivation-path/319?u=bguiz

8

(note that this forum appears to have disabled posting URLs for me, so you’ll need to manually copy-paste the above discourse link)

9

With MetaMask Snaps you can now extend MetaMask’s API to add custom derivation paths, @bguiz .

@CryptoHamilton will be happy to chat with you on how Flask and Snaps works.

1 Like