Bitcoin Watch-Only Wallet: Why You Can See a Balance but Cannot Spend It

A visible balance is not proof of spending access

Bitcoin transaction history is public. An application can display the history of an address supplied by anyone, so a screenshot or a watch-only wallet file is not proof that its holder controls the BTC. There is no network fee that converts a public address into its private key.

Watch-only data can include an address, extended public key or public descriptor. A descriptor describes spending conditions and address derivation; some descriptors contain secrets, so do not publish unfamiliar exports. Public-only data remains useful for monitoring, bookkeeping and preparing unsigned transactions.

First identify the original wallet with the Bitcoin recovery guide. If the input was an old file, the wallet.dat guide explains backup coverage and encryption separately.

First checks: observe, sign or coordinate?

1. Record the app and version and the type of data used to restore it: phrase, wallet file, address or public key.
2. Check wallet information for a watch-only indication and any external signer configuration.
3. Determine whether a hardware device, offline computer or required co-signers were part of the original setup.
4. Compare the expected addresses with old transaction records.
5. Preserve all existing wallet files before creating or importing alternatives.
6. Do not type a hardware wallet's phrase into a website to enable a Send button.

Bitcoin Core's getwalletinfo distinguishes private_keys_enabled from external_signer. Private keys disabled can be expected in a hardware setup. Conversely, keys enabled is not a blanket proof that every displayed output can be spent. The wallet and signing policy have to cover the actual transaction.

An educational watch-only example

Imagine an owner exporting an extended public key from an offline Electrum wallet into an online observer. The online app shows incoming BTC and can prepare an unsigned transaction. It still needs the offline wallet to produce the signature. Electrum documents this as an intentional cold-storage workflow.

If the owner later loses the offline machine, resetting the observer's password cannot replace the lost signing secret. Recovery begins with the offline wallet's backup. If the offline wallet remains available, the problem may simply be completing the documented signing process.

This example is illustrative, not a live test or a client result. Do not use somebody else's sample extended public key as a wallet to receive funds; an address derived from it belongs to that key set.

Where legitimate recovery can begin

For wallet recovery assessment, describe how the wallet was created, what was imported, whether a signer survives, and which backup types you hold. State whether the interface can prepare a transaction but cannot sign it. No private data is needed for that first description.

Recovery may mean reconnecting the signer, restoring the original secret backup or reconstructing a known multisignature setup with sufficient retained keys. It cannot mean calculating a private key from a public address. A file encryption password protects whatever the file actually contains; it does not add missing keys.

Treat an offer to sell you the password for a watch-only wallet with a large balance as unsupported until control is independently established. For assessing providers, use how to choose a recovery company.