search

nvk / walletsrecovery.org

Information about wallet defaults for external recovery
https://walletsrecovery.org/
115 stars 96 forks source link

Missing wallets and/or combos #133

Open nvk opened 3 years ago

nvk commented 3 years ago
tooraj-enayati commented 3 years ago

Please add Trust Wallet as per https://github.com/trustwallet/wallet-core/blob/master/coins.json#L28

"derivationPath": "m/84'/0'/0'/0/0"

Thanks

nvk commented 3 years ago

You can make a pull request here https://github.com/nvk/wallets-recovery/pulls

andronoob commented 3 years ago

Armoury

Bitcoin Armory? It seems to be power-user-oriented, so that I think a over-simple derivation path guide is probably not necessary.

Also, actually I doubt feasibility of self-helped recovery by non-tech-savvy people.

I know little in this field, but I'll take the famous blockchain.info wallet as an example, which has(had) at least three versions of wallet backup format, one of which is even impossible to derive any private key, so that only online recovery from its official website is possible, even the the wallet.aes.json also requires executable binary like its official offline recovery tool.

Sadly, the wallet recovery job has became such a messy stuff which unfortunately does not seem fixable for me.

andronoob commented 3 years ago

BIP39 cannot even prevent such chaos from now on either (it could also be considered that such goal has already failed), as long as developers insist strongly on building incompatible things, just like the case of Electrum2.0 and aezeed, which are even ambiguous to BIP39 (occasionally ambiguous from the machine's view, indistinguishable from the human's view).

Just like the case of FFmpeg/libav that prominent contributors can also act like d*ck because of their strong/stubborn minds, it's probably the inevitable curse/price of freedom.

andronoob commented 3 years ago

There are also implications(comlexities) brought by SegWit, multisig etc - a private key could be (re)used in nonstandard ways, like, a BIP44 privkey got exported and re-imported as a P2SH-P2WPKH privkey by a smartass user, so that the 3-starting P2SH-P2WPKH SegWit address would become invisible to standard BIP44 wallets.