MetaMask / MetaMask/metamask-extension
Unable to derive correct HD path from Trezor
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
### What is this about?
I already have a Trezor device and an account with funds on it created on the device through the Trezor suite software.
I am attempting to connect my Trezor to MetaMask, however, metamask does not appear to call the correct HD path that the Trezor is using and there does seem to be any way to get to it.
Trezor suite gives no option to change HD path natively.
When restoring the hardware wallet metamask actually does offer 2 choices for HDpath, but neither is correct. Could this issue be easily solved by offering more HD path choices other than the default 2?
### Scenario
_No response_
### Design
_No response_
### Technical Details
_No response_
### Threat Modeling Framework
_No response_
### Acceptance Criteria
_No response_
### References
_No response_
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the account-connection and hardware-wallet restoration flow with Trezor Suite and MetaMask, and determine which HD path the funded account uses. No files, tests, or entry points are named; the work is complete when the expected path is established and MetaMask provides a reliable way to select it or otherwise reaches the existing account.
Written by the indexing model from the issue text.
Assessment
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100