Wallet app logout or phone loss: what a recovery phrase can and cannot restore
A recovery phrase can recreate the keys for a compatible self-custody wallet. It does not automatically restore an app login, a custodial account, every wallet type, or the exact screen you saw before. If a wallet appears empty after a reinstall or login, the phrase may be correct while the selected account, network, derivation path or synchronisation state is different.
The first distinction is between an app account and a self-custody wallet. An app account is an identity used to access a service. That service may hold the keys and transaction records, or it may use the account only to manage access to a wallet whose keys are generated and controlled on your device. A self-custody wallet is defined by control of the private keys: the wallet software creates addresses from those keys and uses them to sign transactions. The login used to open the app is not, by itself, a backup of those keys.
If you are locked out or have lost a phone
Do not give a recovery phrase, private key, password or one-time code to anyone offering help. Do not type it into a website or send a screenshot. Use the original app’s documented recovery route if it was an app account, or use a compatible wallet’s established restore/import function if it was self-custody. The exact labels and steps vary by implementation, so a generic recovery guide cannot safely tell you which account or path to select.
If you still have access on another device, first establish what kind of wallet it is and whether the balance is actually visible there. Avoid making changes while you are unsure which wallet you have opened.
What a recovery phrase is
BIP-39 describes a mnemonic sentence as a human-readable way to carry computer-generated randomness. It defines how entropy and a checksum become a list of words, then how that mnemonic is converted into a binary seed. The seed can be used to generate a deterministic wallet through BIP-32 or a similar method.
That is why the phrase can be powerful without being a complete account backup. A compatible implementation must interpret the words in the expected language and order, apply the same optional passphrase if one was used, derive keys using the relevant wallet structure, and scan the relevant addresses. A phrase with an additional passphrase is not the same wallet as the same words without that passphrase. The passphrase is not recoverable from the words.
BIP-39 does not prescribe one universal account layout for every app or asset. BIP-32 describes hierarchical deterministic wallets and says that not all of its features are required by supporting clients. Wallets can therefore differ in derivation paths, address formats, account numbering, networks, script types and rescan behaviour. A phrase can be genuine and still produce no visible balance in a particular implementation.
What it can restore
For a compatible self-custody wallet, the phrase may allow software to recreate the wallet’s signing keys and derive the addresses associated with them. On Bitcoin, wallet software uses public keys or related address information to receive funds and private keys to spend them. The Bitcoin developer guide also separates wallet software from wallet files: a wallet file can contain private keys and other wallet-related information, while a wallet program performs functions such as key generation, transaction monitoring, signing and broadcasting.
A successful restore may therefore recover:
- control of funds held at addresses derived by the expected wallet setup;
- the ability to generate further addresses, where the implementation supports that structure;
- enough key material for compatible software to find and spend the relevant on-chain outputs.
The blockchain is not stored inside the phrase. Bitcoin transactions are public records, and a wallet application normally discovers relevant transactions by scanning or querying the network. The phrase supplies key material; the wallet software still has to derive the right addresses and find the corresponding history.
What it cannot restore
A recovery phrase normally cannot recreate:
- a service login, email address, username, password or two-factor authentication method;
- funds held in a custodial account when the service, rather than you, controls the keys;
- a missing BIP-39 passphrase or another wallet-specific secret;
- an unsupported asset, network, script type or derivation path;
- local labels, contacts, price settings, notification preferences or other app-only data;
- transactions that were never confirmed or records that existed only in a service’s database;
- access to a wallet whose backup was a different format, such as a raw key, encrypted wallet file or provider-specific export.
A phrase also cannot reverse a transaction that has already been authorised and confirmed. It restores key control, not an earlier state of the transaction record.
Why the restored wallet may look empty
An empty screen is evidence of a mismatch or missing data, not proof that the funds have vanished. Common explanations include:
- The wrong layer was restored. You reopened an app account, but the self-custody wallet was a separate profile, or you restored a self-custody phrase where the original balance was held by a service account.
- A different passphrase was used. In BIP-39, changing the optional passphrase changes the derived seed. A blank wallet can be the expected result of a wrong passphrase.
- A different account or derivation path was selected. Wallets may derive addresses along different paths or account indexes. The same words can lead to different address sets when the implementation makes different choices.
- The network or address format is different. A wallet can be looking at another network or script/address type, so it does not display the outputs you expect.
- The wallet has not finished discovering history. A restore can require a network connection, a rescan or an indexer response. Local display may lag behind the on-chain record.
- The wallet was watch-only or otherwise incomplete. A public-key or address-only view can show history without containing the private keys needed to spend.
- The original backup was not a BIP-39 phrase. Word count alone does not identify the format. Some wallets use other mnemonics, raw keys, encrypted files or service-specific backups.
Do not keep guessing passphrases or importing the phrase into random software. Each attempt can create more confusion and exposes the secret to another environment. Check the original wallet’s documentation and the backup format you actually created. If you cannot establish the format and the relevant derivation details, treat the case as unresolved rather than assuming the balance is gone.
Incident checklist
- [ ] Stop replying to anyone who asks for your recovery phrase, private key, password, one-time code or remote access.
- [ ] Identify whether the missing access was an app/service account, a self-custody wallet, or a watch-only view.
- [ ] Check whether another authorised device still shows the wallet and its transaction history.
- [ ] Locate the original backup record without copying the phrase into chat, email, a form or an unverified website.
- [ ] Confirm the backup type, word order, language and whether an additional passphrase was used.
- [ ] Use only the documented recovery path for the relevant implementation.
- [ ] Check the selected network, account, address type and derivation settings before concluding that the wallet is empty.
- [ ] Allow for synchronisation or rescanning where the software documents it.
- [ ] Compare a known receiving address with the relevant public blockchain record, without publishing the address alongside personal information.
- [ ] If funds appear to have moved without your authorisation, preserve dates and transaction IDs and use an official reporting or support route. Do not send secret credentials as evidence.
The short version
A recovery phrase is a backup of key-generating material for a compatible self-custody wallet. It is not a universal “log back in” code. Whether it restores anything visible depends on the wallet format, optional passphrase, derivation choices, network, address type and the software’s ability to rescan the chain. A newly opened wallet that shows zero can be the wrong account or an incomplete scan, but it can also mean the original backup was different or the funds were held by a custodial service.
For background, read The Coin Expert’s guide to crypto wallets, private keys, addresses and seed phrases, the digital assets hub and the guide to crypto scams, phishing and fake support. None of these pages asks readers to submit a recovery phrase or other secret.
Sources
- Bitcoin Developer Documentation, Wallets. Defines wallet programs and wallet files, and describes the roles of public keys, private keys, signing and networked wallet software.
- Bitcoin Improvement Proposal 39, Mnemonic code for generating deterministic keys. Defines mnemonic generation and conversion to a binary seed, and notes that the seed can generate deterministic wallets using BIP-32 or similar methods.
- Bitcoin Improvement Proposal 32, Hierarchical Deterministic Wallets. Describes deriving a tree of key pairs from a seed and notes that supporting clients do not have to implement every feature.
- Bitcoin Developer Documentation, Transactions. Explains the relationship between private keys, public keys, addresses and spendable transaction outputs.
Source check: 23 September 2026. This is general educational information, not financial, legal or technical support advice. Never publish or share a recovery phrase, private key, password or one-time code.