A fork wallet is a Bitcoin wallet in a different coat.

The same encryption, with a backend caveat

These Core-derived clients — Litecoin Core, Dogecoin Core, Bitcoin Cash node wallets from the Core codebase, Dash Core and others — forked from Bitcoin Core at various points, and the wallet encryption code carried over: the same AES-256-CBC encryption, the same iterated-SHA-512 key derivation, and the same dynamic iteration counts. One caveat before you assume a byte-identical file: the name wallet.dat does not tell you which database backend is inside. Modern Bitcoin Core descriptor wallets (0.21+) use SQLite, legacy Bitcoin Core wallets use Berkeley DB, and forks vary — Dogecoin Core, for example, still uses Berkeley DB. For the legacy encryption structures, the rules below apply. That means:

• the encryption is AES-256-CBC, with the master key protected by the same iterated-SHA-512 key derivation;
• the iteration count is dynamic — chosen when the wallet was first encrypted, which is why old wallets crack far faster than new ones (how wallet encryption works explains the mechanism);
• the measured speeds apply: a low-round wallet (reference ~68k iterations) checks at ~472 guesses/sec and a high-round one (reference ~267k) at ~122/sec on a typical modern CPU — roughly 4× apart, but the gap follows the rounds count, not the client version (btcrecover measurements).

So the summary: the cracking-time math, the calculator, and the feasibility framework all apply unchanged.

Where the wallet.dat lives (fork versions)

Paths are the clients’ documented defaults, and the data directory may differ by version or a custom datadir. Do not assume every Core-derived fork made the same Windows data-directory change: Bitcoin Core’s current Windows default is %LOCALAPPDATA%\Bitcoin with legacy %APPDATA%\Bitcoin still relevant, while for Dogecoin Core check %APPDATA%\Dogecoin first, and for Litecoin Core check %APPDATA%\Litecoin first unless the specific installed version documents otherwise — search %LOCALAPPDATA% as an extra fallback for each. If the file isn’t where you expect, the OS-wide search methods on how to find your wallet file will locate it. Note that some forks kept the Bitcoin directory name — searching for wallets/wallet.dat without a coin name catches them all.

The unlock path is identical to Bitcoin Core

1. 1
   Secure copies first. Copy wallet.dat to several safe places before anything else — see protect your wallet files.
2. 2
   Check whether it’s even encrypted — without relying on startup prompts. An encrypted wallet can load and display information while locked, so “it opens” proves nothing. On a safe working copy with a matching Bitcoin Core version, use getwalletinfo in the client console: with passphrase encryption it reports unlocked_until, where 0 means the wallet is currently locked. Do not use “does the GUI ask at startup?” as an encryption test, and do not run recovery files in newer clients that might migrate them.
3. 3
   Try the unlock command. In the client’s console: walletpassphrase (or the GUI prompt). One careful attempt is fine — this is not a hardware wallet, there is no wipe-after-N-tries.
4. 4
   If it fails, it’s a cracking case. The exact procedure — wallet header check, iteration extraction, token-list attacks with btcrecover — is on the wallet.dat guide. The tools don’t care whether the coin is Bitcoin or Litecoin; the legacy encryption format is what matters — modern SQLite descriptor-wallet backends are a separate case.

What is different for forks

• Your password is verified against a wallet, not a coin. A password from a 2014 Litecoin wallet works only on that wallet file — but if you know the pattern you used across wallets, one recovered pattern can unlock several.
• Old fork wallets are the easiest recovery cases in crypto. A Dogecoin wallet encrypted in 2014 used era-appropriate (low) iteration counts. Same password, far faster search than a 2023 wallet.
• Watch out for “wallet.dat is empty” confusion. Some forks display empty balances if the client can’t read the file. Encrypted files look like random bytes — the file identifier and the header checks in the wallet.dat guide will tell you if you’re looking at a real, encrypted wallet.

Next step

Open the wallet.dat guide and follow it as if you had a Bitcoin wallet — because technically, you do. And if the amounts are meaningful, the real numbers on what’s actually recoverable will keep your expectations realistic.

Frequently asked questions

Sources & references

1. btcrecover — performance benchmarks
2. Bitcoin Wiki — wallet encryption