MetaMask / MetaMask/metamask-extension
Wallet contract (created in Mist or Ethereum wallet) not appearing/can't be imported
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
I've been looking for an issue filed or documentation in this matter but haven't been able to find it. Apologies if this is duplicate/well known. I have a wallet contract that was created by an account, call it "Main". When I import "Main" via keystore or via private key (I've tried both, on both chrome and brave) the wallet contract can't be imported afterwards (mist/ethwallet wallet contracts don't have a private key themselves).
Is there a way -- any way, even scripting something on the JS console will work-- to get the wallet contract to appear in metamask and be usable like other accounts? And if not, if this something that's on the roadmap?
thanks!
Contributor guide
Research direction
The issue names no files, tests, or entry points. First clarify whether MetaMask should support importing and using wallet contracts created in Mist or Ethereum Wallet, then investigate the existing account-import behavior and project roadmap; done means the supported workflow is documented or the capability works as requested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100