Wallet Password Recovery (wallet.dat / keystore) — An Owner-Authorised Guide

In one paragraph. If you have your encrypted wallet file — a Bitcoin Core wallet.dat, an Ethereum keystore JSON, an Electrum wallet file — but you have forgotten the password that unlocks it, your coins are not gone. The keys are inside the file; the password is the lock, and a lock can be worked on. Recovering a forgotten wallet password is a controlled, owner-authorised technical process that depends almost entirely on two things: how the wallet was encrypted and how much you remember about the password you chose. It is not "hacking", it is slow by mathematical design, and it is honest about its limits — a truly random 16-character password is, and should be, beyond reach. This guide explains how it works, what makes a case feasible, and the verification we require before we touch a single file.

1. Password recovery is not hacking — and why that distinction matters

This is the first thing to be clear about, because it is the difference between a legitimate service and a crime.

Hacking is defeating the security of an asset that is not yours, without authority, to take it. Password recovery is the rightful owner regaining access to their own asset, with their authority and their cooperation, using the hints only the owner can provide. The technical operations may rub shoulders — both involve testing candidate passwords against an encrypted file — but the legal and ethical character is opposite, and the dividing line is authorisation and ownership.

That line is not rhetorical for us; it is operational. Before we begin any password recovery we verify that you are the rightful owner of the wallet (see §6). We do this because it is the right thing to do, because UK money-laundering and fraud law requires it, and because the entire premise of the service collapses if it is offered to anyone other than the owner. A firm that will run a password recovery on a wallet file without establishing ownership is not offering you a service — it is advertising a crime, and you do not want your wallet anywhere near it.

Everything in this guide assumes you are the verified owner recovering your own wallet.

2. What an "encrypted wallet" actually is

It helps to picture what you are actually locked out of.

Your coins are not in the wallet file. They are entries on a blockchain, controlled by a private key. The wallet file stores that private key (or the seed it derives from) in encrypted form. When you set a wallet password, the software did not just "set a password" — it used your password to encrypt the keys, so that the file on disk is useless without it. The password is the only thing standing between the encrypted blob and the key inside.

The common cases we see:

• Bitcoin Core wallet.dat — the classic. Often created years ago, encrypted with a password the owner half-remembers. The keys are inside; the password decrypts them.
• Ethereum keystore JSON (UTC/V3) — a small JSON file (sometimes called a "keystore" or "UTC file") that stores one encrypted private key, protected by a password and a key-derivation function (usually scrypt or PBKDF2).
• Electrum / other wallet files — various formats, generally a seed or key set encrypted under a user password.

In every case the recovery question is the same: can we find the password that decrypts this file, given what the owner remembers and how slow the encryption makes guessing?

Critical: do not modify or "repair" the wallet file. Make a copy, work only from the copy, and never run "repair" tools on the original. A corrupted wallet.dat is a far worse problem than a forgotten password, and some well-meaning "fix-it" utilities damage the file. Preserve the original untouched.

3. Why password recovery is slow by design — key-derivation functions

Here is the technical heart of the matter, and the reason an honest firm cannot promise speed.

Wallet software does not check your password by simple comparison. It runs it through a key-derivation function (KDF) — PBKDF2, scrypt, or Argon2 are the common ones — which is deliberately expensive to compute. The KDF takes your password and grinds it through thousands or millions of internal iterations (and, for scrypt and Argon2, a large chunk of memory) to produce the decryption key. This is a feature: it means an attacker testing billions of passwords pays that expensive cost per guess, which is what makes a good password safe.

For recovery, that same feature is the obstacle. Every candidate password we test must be run through the full KDF before we know if it is right. So the speed of recovery is governed by:

1. Which KDF the wallet uses, and how hard it is tuned. An older wallet with a low iteration count is far faster to search than a modern one with a heavy scrypt/Argon2 setting. The difference can be several orders of magnitude.
2. The size of the password space we have to search — which depends entirely on §4 and §5.
3. The hardware. GPU-accelerated search tests many candidates in parallel and is dramatically faster than a single CPU for the KDFs that suit it; some memory-hard KDFs resist GPU acceleration by design and stay slow regardless.

The honest consequence: a short or pattern-based password on an older wallet can fall quickly, while a long high-entropy password on a modern memory-hard KDF can be effectively impossible — not because we lack tools, but because the mathematics says so. We keep the specific tooling and hardware configuration internal, but the physics above is what determines your odds, and any firm that quotes you a guaranteed timeline without first asking which KDF your wallet uses is not being straight with you.

4. The number that decides everything — password space

The feasibility of a password recovery is, at its core, one calculation: how many candidate passwords might it be, and how fast can we test one?

A password drawn from a character set of size C, of length L, has up to Cᴸ possibilities. The exponent is what bites:

Two things change this picture completely, one for the worse and one for the better:

• The KDF cost multiplies the wall-clock time for every figure in that table. A space that is "feasible" against a cheap KDF can be "impossible" against a memory-hard one.
• What you remember divides the space, often by many orders of magnitude. This is the entire game, and it is the subject of §5.

The takeaway: a truly random long password is beyond recovery, and we will tell you so rather than take your money. But almost nobody chooses a truly random password they then forget — people forget passwords that had a structure, and structure is recoverable.

5. What you remember is the recovery — building the search space

A blind search of all possible passwords is hopeless past a short length. A search guided by what the owner remembers is a different problem entirely, and it is the one that succeeds.

The most valuable things you can recall, roughly in order of impact:

• Approximate length — "it was about 10 or 11 characters" removes everything shorter and longer.
• Character composition — "all lowercase plus a number at the end", "no symbols", "a capital at the start". Each constraint slices the space.
• Your password habits from that era — the base words you reused, the way you substituted a→@ or s→$, the years or names you appended. People are far more consistent than they think across the passwords of a given period.
• Candidate base words or phrases — a pet's name, a street, a band, a phrase. A handful of base words with your known mutation patterns is a tiny, fast search.
• Where it sits between two known passwords — sometimes you remember it was "like my email password but with an extra digit".

A reconstruction takes these and builds a targeted candidate set — known bases, your mutation rules, the right length and composition — instead of a blind sweep. This is why two cases with the "same" forgotten password can be hours apart in difficulty: the one with good recalled structure is small, the one with "no idea, it was random" may be infeasible. At scoping we work through exactly this with you, and the quality of these hints is the single biggest predictor of success.

6. Owner verification — why we insist, and what it involves

Because §1 is not negotiable, we verify ownership before any technical work. This protects you (it is part of why your funds cannot be quietly taken) and it is required of us under UK anti-money-laundering and know-your-customer obligations.

In practice, verification is proportionate to the value and the circumstances, and typically involves:

• Identity — confirming who you are, to the standard our compliance procedures require.
• A credible account of ownership — how you came to hold the wallet, when it was created, and evidence consistent with that (transaction history, related addresses, prior correspondence, device provenance).
• For inherited or estate wallets — the relevant probate or authority documents. This overlaps with our Inherited Wallet Recovery guide, and executors should start there.
• Sanctions and AML screening — standard checks we are obliged to run.

If a case cannot clear ownership verification, we will not proceed — and that is a feature, not an obstacle. The discipline that stops us working on a wallet whose ownership is unproven is the same discipline that stops anyone else doing it to your wallet.

7. How we handle the file — non-custodial, offline, contained

The handling principles mirror the rest of our work:

• Strictly non-custodial. We recover the password; we never take custody of your coins. When the password is found, it is delivered to you, encrypted, and you open your wallet and move the funds to a fresh wallet under a new password or seed. At no point does recovering a password require us to control the asset.
• Offline and contained. The wallet file is handled on an isolated machine, never uploaded to an online "service". Communications are encrypted, the working copy is minimised to what the search needs, and the wallet file and all derived material are securely deleted on completion.
• A fresh wallet afterwards. A wallet whose password you once forgot — and which has passed through a recovery — should not be your long-term home for the funds. We recommend moving recovered funds to a newly generated wallet, and we will walk you through that at handover.

This kind of work spans Tier 2 to Tier 3 depending on the KDF and the search space: a short, well-remembered password on an older wallet is lighter work; a long password needing sustained GPU search sits alongside our Tier 3 model, with its honest deposit-and-success-fee structure. We price the work in advance, in writing, and quote the realistic odds before you commit.

8. What NOT to do

• Do not upload your wallet file to any online "recovery service", website, or form. Your encrypted wallet.dat or keystore contains your keys; handing it to an unverified online party is handing over the wallet. Legitimate recovery never asks you to upload the file to a web page.
• Do not modify, "repair", or run fix-it tools on the original file. Work only from a copy and keep the original pristine. A damaged wallet file is worse than a locked one.
• Do not guess passwords endlessly in the live wallet software, especially where repeated failures can corrupt state or trigger protective lockouts. Capture what you remember on paper instead.
• Do not share the wallet file over unencrypted channels — plain email, chat apps, cloud links. Anything that leaves an uncontrolled copy is a risk for the life of that copy.
• Do not pay for a "preliminary analysis" before a written engagement. Proper scoping is free. Charging to "look at your wallet" before quoting is monetising the look, because there is no job behind it.
• Do not pay in cryptocurrency, and avoid anyone who insists on it. Reputable UK firms invoice in GBP, take bank transfer or card, and issue VAT invoices.
• Do not trust any promise of "guaranteed" password recovery. As §3–§5 show, feasibility is governed by the KDF and your recalled structure. Anyone guaranteeing a result has either not asked the right questions or is not being honest.

9. Frequently asked questions

I have my wallet.dat but forgot the password. Are my coins recoverable? Possibly, and often yes — it depends on the encryption and on what you remember. The keys are inside the file; the password is the lock. A short or pattern-based password is frequently recoverable; a long, truly random one may not be. A free assessment will give you a realistic probability rather than a guess.

Is this legal? It sounds like cracking. It is legal when, and only when, it is the rightful owner recovering their own wallet — which is why we verify ownership before starting (§6). The technical steps resemble cracking; the authorisation and ownership make it a legitimate service. We do not work on wallets whose ownership cannot be established.

How long does it take? It depends on the key-derivation function and the size of the search space your hints leave. A well-remembered password on an older wallet can resolve quickly; a large search on a memory-hard KDF can take days of GPU time or prove infeasible. We give you a realistic range at scoping, not a marketing timeline.

What if my password was completely random and I remember nothing? Then be prepared for an honest "no". A truly random long password against modern encryption is beyond practical reach, and we will tell you that at assessment rather than take a deposit for a search that cannot finish. The good news is that genuinely random and forgotten is rare — most forgotten passwords had a structure.

Do you need my wallet file to give me a quote? No. To scope, we need the wallet type and version, the KDF if known, and a description of what you remember about the password. The file itself is only handled once a written engagement and ownership verification are in place.

Can you recover an Ethereum keystore / MetaMask password the same way? A keystore JSON (UTC/V3 file) follows the same model — an encrypted private key behind a password and a KDF — and the same feasibility logic applies. Browser-extension wallets vary; tell us exactly what you have at first contact and we will tell you whether it fits this workstream.

Which jurisdictions do you serve? The UK, the EU, and most jurisdictions where we can complete sanctions and money-laundering checks. We do not currently engage clients resident in the United States or Canada. If unsure, ask at first contact.

10. Working with us

Step one — a written first contact: an email to legal@arcana-crypto.com describing your wallet type and what you remember about the password. Do not send the wallet file in the first email.

Step two — a free, confidential assessment. We tell you whether the case looks feasible, give a probability range and indicative cost, and explain the ownership verification we will need. If it is not worth pursuing, we will say so.

Step three — if you proceed, ownership verification and a written engagement letter come first; only then is the wallet file handled, on an isolated machine, and the recovered password delivered to you encrypted.

If the process ever feels rushed, slow it down. Your encrypted file is not deteriorating, and patient recovery beats a careless leak every time.

A closing note. A forgotten wallet password feels like a slammed door, and the temptation is to throw the file at the first website promising to open it — which is exactly how owners lose the coins the password was protecting. The steadier truth is that your keys are still inside that file, the lock can often be worked on when you remember the shape of what you chose, and a recovery done properly never requires you to hand over custody of anything. Preserve the original file, write down everything you remember, and if you want an honest read on your odds, write to us — legal@arcana-crypto.com.

Arcana Crypto LTD — registered in England and Wales (no. 16371124). Recovery and forensics for cryptoasset wallet-loss cases. UK + EU engagements. Sole Director: R. Macri.

Guide version 1.0 · Published 14 June 2026 · Last reviewed 14 June 2026 · Reviewed by counsel. This guide is general information, not legal or financial advice. The engagement letter is the operative contract for any recovery engagement, and its specific terms — not this guide — govern the relationship.