Which situation are you facing?
Recovery conditions differ substantially between problems. Find the closest match, note which actions could destroy clues, and then decide what to do next.
01 · Forgotten wallet password
Common cases: mobile wallet payment or transaction password; browser-extension unlock password; encrypted Keystore or wallet.dat password.
Avoid for now: uninstalling the wallet, clearing its data, resetting the device, or repeatedly guessing until it locks.
Possible path: check whether a valid backup offers another access route; organize password-habit clues and assess the range that can be tested.
Mobile wallet password assessment guide →
02 · Incomplete or out-of-order seed phrase
Common cases: several words missing or partly unclear; uncertain word order or copying errors; uncertainty about an extra passphrase.
Avoid for now: testing a seed phrase on an unfamiliar website, photographing it or publishing the actual words.
Possible path: record the total number of words, how many are missing and their positions; compare candidates against a known address. Consider computing resources only if the verification task is suitable for parallel work. (Detailed guide in Chinese.)
Seed phrase verification guide (Chinese) →
03 · Wallet file deleted or damaged, or an old device has failed
Common cases: wallet.dat or a Keystore file was deleted or overwritten; an old computer, drive or phone will not start; only part of a backup was found.
Avoid for now: installing recovery software or saving results to the original drive; repeatedly powering up and scanning a failing device.
Possible path: preserve the original separately from a working copy; assess “found,” “decrypted” and “matches the target address” as separate conditions. (Detailed guide in Chinese.)
Wallet-file preservation guide (Chinese) →
04 · Address mismatch or assets missing after import
Common cases: a seed phrase is accepted but the balance is zero; the imported address differs from the one in your records.
Avoid for now: immediately deciding that the backup is invalid or repeatedly importing it into multiple tools.
Possible path: check the chain, address type and account index, then check the derivation path and any extra passphrase. (Detailed guide in Chinese.)
Five checks for an address mismatch (Chinese) →
05 · Unrecognized transaction; assets have been transferred
Common cases: a private key or seed phrase may have been exposed; tokens were transferred after a phishing approval was signed.
Avoid for now: trusting strangers who claim they can “reverse” a transaction or continuing to use a wallet that may be compromised.
Possible path: preserve the chain, transaction hash and timeline; distinguish key exposure from a suspicious approval before choosing a response channel.
Review the incident response process →
06 · Only an address, balance screenshot or transaction record
Common cases: you remember an address but cannot find the source of its keys; you need to clarify the recovery objective and evidence limits.
Avoid for now: treating visible funds as proof they can be recovered or believing claims that a private key can be derived from an address.
Possible path: use on-chain records to establish the target address and timeline, then look for an actual backup, old device or custodial platform channel.
What on-chain evidence can establish →
Four steps from first contact to completion
At the end of each step, we explain what has been confirmed and what is still missing. You decide whether to continue.
- Confirm authorization and the asset: verify wallet ownership, the engagement or delegation relationship, target address and scope that may be handled. You receive: a statement of the permitted scope.
- Protect original data: agree on preservation methods and keep originals separate from working copies to prevent further damage to clues. You receive: preservation recommendations and a materials checklist.
- Assess clues and provide a quote: organize password clues, missing seed phrase details and wallet version; assess feasible paths and expected effort. You receive: a feasibility conclusion and written scope and fee terms.
- Perform the agreed work and independently verify: follow the agreed scope, provide an independent check, verify the address relationship and then plan a secure migration. You receive: verification results and migration recommendations.
How fees are determined
Wallets and available clues differ, so there is no universal price list. Fees are confirmed in writing after assessment and before work begins.
- Describe the issue in text. Give an overview only; do not send a seed phrase, private key, password or wallet file.
- Assess feasibility and effort. We explain confirmed facts, missing conditions and paths that could be tested.
- Confirm scope and fees in writing. The agreement states the work scope, deliverables, stop conditions and payment arrangements.
- Work begins only after both sides agree. If the scope changes, additional work is confirmed separately before it starts.
Factors that affect the amount of work
- Wallet type and version.
- Condition of the materials and devices.
- Quality of clues, including password clues and the number and positions of missing words.
- Computing resources required.
- Deliverable requirements.
We confirm the scope before paid work, state stop conditions in advance and do not include unapproved additions in the original engagement. An assessment, agreed fee or accepted engagement does not promise that a wallet can be recovered or assets returned. See the full methodology and scope description (Chinese).
Questions before an inquiry
I forgot my wallet password. What should I do first?
Record the wallet name, device state and error. Check whether a seed phrase, private key, encrypted file or other valid backup remains. Until the backup is confirmed usable, do not uninstall the wallet, clear data or reset the device. App unlock passwords, encrypted-file passwords and extra seed phrase passphrases have different roles and recovery paths.
Some seed phrase words are missing, or I do not remember the order. Is an assessment worthwhile?
Preserve the original transcription and record the total word count, number missing, whether positions are known and the original wallet type. Do not publish the actual words. A testable range also depends on word order, backup format, any extra passphrase and target address; the number of missing words alone cannot guarantee a result.
Can a private key be recovered from a wallet address and balance alone?
No. A public address, balance, transaction hash or identity document cannot by itself reveal the private key or seed phrase for an ordinary self-custody wallet. An address can help verify on-chain records but cannot replace signing authority.
How are assessment and follow-up work priced?
Fees depend on the actual issue, the materials and agreed scope. Before paid work starts, confirm the quote, deliverables, stop conditions and other terms. Do not infer your fee from a similar scenario.
Can you guarantee success or give a standard duration?
No. Recovery and a standard turnaround time cannot be promised before conditions are verified. Backup integrity, password conditions, device state, wallet version and actual authority all affect the assessment. Review evidence and limitations before deciding on next steps; feasibility assessment does not equal successful recovery.
More answers are available in the wallet recovery FAQ.
Does the recovery task need substantial parallel verification?
CZB's second business is an idle-computing collaboration network, planned to organize distributed GPU and PC resources for authorized tasks suited to parallel verification. The network is still being prepared and is not accepting node connections. Computing resources are not a substitute for missing recovery conditions or a guarantee of success.