MetaMask / MetaMask/metamask-extension
[Bug]: Can't see or manipulate $ETC funds when using MetaMask to access the Ledger hardware wallet.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
### Describe the bug
When I try to access my funds I see 0 $ETH, my rpc is set to several services but it still shows $ETH in stead of $ETC.
Also changing the derivation path does not solve this issue.
### Steps to reproduce
1. set RPC to Ethereum Classic
2. Connect Ledger hardware wallet to Metamask
3. Open Ledger Live and open Ethereum App
4. Open device bridge through websocket
5. select the HD path "Ledger Live" => no success
6. select the HD path "Legacy (MEW/Mycrypto) => no success
7. select the HD path "BIP44 standard(e.g. MetaMask, Trezor)" => no success
### Error messages or log output
```shell
Select an account:
They all show 0 $ETH
```
### Version
10.20.0
### Build type
_No response_
### Browser
Firefox, Brave
### Operating system
Windows, MacOS, Linux
### Hardware wallet
Ledger
### Additional context
Contacted support before but they send me a manual how to use the hot wallet, they couldn't acknowledge the bug in combination with the Ledger hardware wallet. Now I try this approach to solve this.
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 Ledger hardware-wallet flow in MetaMask with an Ethereum Classic RPC, checking account selection across the listed Ledger Live, Legacy, and BIP44 derivation paths. Inspect the Ledger device bridge websocket and account/network handling; done means ETC accounts show the expected balances and can be manipulated rather than appearing as zero ETH.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100