A watch-only Bitcoin wallet separates monitoring from signing. It can display transactions and balances using public wallet data, while the private keys remain on a hardware wallet or another offline signer. That split is useful for treasury checks, payment tracking and day-to-day account visibility. It does not prove that the person viewing the wallet can spend the bitcoin.
What the wallet can know
The scope depends on what you import. A single address reveals activity for that address. An account-level extended public key can derive a sequence of non-hardened child public keys, so compatible software may follow many receiving and change addresses. BIP 32 defines extended public keys as a public key paired with a chain code and explains the child-key derivation model.
An output descriptor can describe more than an xpub alone. It tells software how keys map to output scripts and can include derivation paths and ranged keys. BIP 380 defines descriptor syntax and checksums. A checksum helps catch transcription mistakes, but it does not prove that a descriptor came from your wallet. Descriptors may also contain private material, so check the export before moving it to an online device.
What it cannot do by itself
Public wallet data does not supply a valid signature for a spend. Some watch-only applications can build an unsigned transaction, but a separate signer must inspect and authorize it. BIP 174 defines the Partially Signed Bitcoin Transaction format so different tools can pass transaction data and signatures between coordinators and signers.
This distinction also explains a common scam. Anyone can import a public address and display its real balance. The display says nothing about who controls the keys. A seller who offers a funded watch-only wallet, then asks for an activation fee, has not demonstrated ownership. The practical test is whether the claimed owner can produce a valid spend under the wallet’s signing policy.
Choose the smallest useful export
Use one address when the job is to monitor one payment destination. Use an account export only when the watcher needs broader history or must generate addresses. An xpub or public descriptor can reveal a connected set of past and future activity to the device, app provider or person receiving it. It is public-key data, but it is still sensitive financial information.
Full-account monitoring also depends on correct configuration. Receiving and change branches may be separate. A watcher that follows only the external branch can miss change returned after a spend. The address type, derivation path and range must match the signing wallet. Do not fix a mismatch by entering a seed phrase into the monitoring app.
A safer setup check
- Protect and test the signing wallet and its recovery backup first.
- Export only the public address, xpub or public-only descriptor needed for the task.
- Import it into software obtained through the provider’s official channel.
- Compare several past transactions and the next receiving address with the signer.
- Verify every destination, amount, fee and change output on the signing device before approval.
A watch-only copy can reduce the consequences of losing a monitoring phone because the phone lacks signing keys. It cannot protect against a false receiving address, an exposed account history, a bad backup or careless approval on the signer. Keep the monitoring scope narrow and treat any unexplained balance or address mismatch as a reason to stop.
Adapted from Watch-Only Wallet Explained: Track Bitcoin Without Private Keys.