How to Create a Watch-Only Bitcoin Wallet in Electrum

Understanding Watch-Only Wallets

1. A watch-only Bitcoin wallet in Electrum does not store private keys locally.

2. It relies entirely on externally managed signing infrastructure or hardware devices for transaction authorization.

3. The wallet displays real-time balance and transaction history by scanning the blockchain using public key information.

4. Users retain full visibility over UTXOs associated with imported addresses or extended public keys (xpubs).

5. This model eliminates exposure of secret material on potentially compromised desktop environments.

Step-by-Step Setup Process

1. Launch Electrum and select Create a new wallet during initial setup or via File → New/Restore.

2. Choose Standard wallet, then click Next until reaching the wallet type selection screen.

3. Select Watch-only wallet instead of default options like “Create a new seed” or “Import Bitcoin addresses”.

4. Paste one or more Bitcoin addresses, an xpub, or a descriptor string into the input field provided.

5. Confirm the import and allow Electrum to synchronize with the network using its built-in server pool or a custom backend.

Descriptor-Based Import Options

1. Modern Electrum versions support BIP-32, BIP-44, BIP-49, and BIP-84 descriptors for deterministic address derivation.

2. An example descriptor: pkh([d0a57b8e/44'/0'/0']xpub6C.../0/*) — this enables automatic scanning of all receiving addresses under that path.

3. Descriptors allow precise control over derivation paths and eliminate ambiguity when importing from multisig setups or legacy wallets.

4. Electrum validates syntax before initiating synchronization, rejecting malformed or unsupported formats immediately.

5. Imported descriptors are stored in the wallet file but contain no cryptographic secrets — only public data and metadata.

Security Implications and Limitations

1. Watch-only wallets cannot sign transactions without external intervention — no private keys exist within the software environment.

2. Signing must occur through connected hardware wallets, air-gapped devices, or manual PSBT workflows.

3. Balance inaccuracies may appear if servers fail to return complete historical data for imported addresses.

4. Electrum’s default server infrastructure does not guarantee full archival node behavior — gaps in history can occur depending on server configuration.

5. Users should verify balances against independent block explorers or self-hosted full nodes when high assurance is required.

Frequently Asked Questions

Q: Can I send Bitcoin from a watch-only wallet?A: No. Sending requires access to private keys, which are intentionally excluded from watch-only mode. You must use a separate signing device or generate PSBTs for offline signing.

Q: Does importing an xpub expose my entire wallet structure to Electrum?A: Yes. Electrum will derive and monitor all addresses generated under that xpub according to the specified derivation path, revealing address patterns and balance distribution to the client and any connected servers.

Q: Is it safe to use Electrum’s default servers with a watch-only wallet?A: Server operators can observe which addresses you’re monitoring and infer usage patterns. For enhanced privacy, configure Electrum to connect to your own Bitcoin Core node or a trusted ElectrumX instance.

Q: What happens if I lose the wallet file after setting up a watch-only wallet?A: Since no private keys are stored, losing the file only means re-importing the same addresses or descriptors. No funds are at risk, but UI state and label data will be gone unless manually backed up.