> how password recovery works
Modern wallet files (wallet.dat, keystore v3, MetaMask vault, etc.) protect keys with a KDF-hardened password. We use custom GPU rigs to test candidate passwords against the vault. The critical input is your MEMORY — not the file.
What we ask you for:
- Length range (was it 8 chars? 20+?)
- Character sets you tend to use
- Words, dates, names, or phrases you might have based it on
- Old passwords you know you've reused elsewhere
- Any partial recall ("I think it started with…")
> supported wallet formats
· Bitcoin Core / Bitcoin Knots — wallet.dat
· Ethereum keystore v3 (Geth, Parity, MEW, MetaMask exports)
· MetaMask browser vault (LevelDB extracted)
· Electrum — encrypted mnemonic and password-protected wallet files
· Blockchain.info (old .aes.json)
· Trust Wallet, Rainbow, Phantom vaults
· BIP-38 encrypted paper wallets
> what makes success likely
Success correlates almost linearly with how much you can narrow the search space.
High odds: you remember most of it and just want to test variations.
Medium odds: you remember the theme (a phrase, a name, a pattern) but not exact chars.
Low odds: fully random password with no memory hooks.
We tell you which bucket you're in during the free assessment. No point taking a case we can't win.
> safety practices
· We work on isolated, air-gapped compute nodes.
· Vault files (or hash-only extracts) are wiped after case closure.
· You sign a chain-of-custody document. So do we.
· We never move funds. Once the password is found, YOU authenticate to the wallet and move your own assets. Our job ends there.