MetaMask / MetaMask/metamask-extension
(Ext) Add custom HD derivation path option for Trezor
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
The custom derivation path was merged for Ledger https://github.com/MetaMask/metamask-extension/pull/9367 (it is not yet available as of version 9.5.4, though).
Something similar might be needed for Trezor's integration too:
> @vondra: I moved from Ledger to Trezor. I need to connect to m/44'/60'/0' addresses. When I connect Trezor is there a option how to manualy set derivation path or invoke the path selector ?
[Comment](https://github.com/MetaMask/metamask-extension/issues/6716#issuecomment-836727593)
[This support article](https://metamask.zendesk.com/hc/en-us/articles/360060331752) will need to be updated once the Custom Derivation Path is available for either Ledger or Trezor.
Contributor guide
Research direction
Start by comparing the Ledger custom derivation path implementation in pull request #9367 with the existing Trezor integration. Confirm the requested m/44'/60'/0' path behavior and review the linked support article. Done means Trezor offers the equivalent custom path option and the support article reflects its availability.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- documentation, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100