Crypto Security
6 min

Bitcoin Wallet Safety: Share Addresses, Not Private Keys

Understand Bitcoin addresses and xpub privacy, verify payments, keep recovery secrets offline, and respond to lost access or suspected exposure.

LOCK.PUB
Published: Updated:
Bitcoin Wallet Safety: Share Addresses, Not Private Keys

Receiving Bitcoin or coordinating with family does not require sharing a private key. Separate payment information from the authority to spend or restore the wallet.

An address is not a recovery secret

A receiving address can be given to a payer. It does not, by itself, let them spend your bitcoin, but public blockchain records can reveal transactions and link activity to you. Share only what the payment requires.

An extended public key, or xpub, is different from one receiving address. It can derive a set of public addresses and allow observation of their activity without spending authority. That wider visibility is a privacy risk. Do not publish an xpub or send it to a payer who only needs an address. BIP32 describes this separation between public derivation and private signing. Wallet files, recovery words and private-key QR codes are not public payment details.

Verify the recipient without exporting keys

Use the wallet's receive function and confirm the Bitcoin network. Check the complete address through a trusted channel and, for a hardware wallet, its own screen according to the manufacturer's instructions. Do not rely on a matching beginning and ending or copy an address from transaction history alone.

Receiving a payment does not require giving support staff a seed phrase, signing an unexplained request or granting remote access. Follow Bitcoin.org's wallet-security guidance and your specific wallet's documentation.

Keep recovery secrets offline

Do not put private keys, recovery phrases, PINs or recovery passphrases into LOCK.PUB, online notes, password managers, photographs or cloud storage. Encrypting an online copy does not remove the risks of a compromised device or service. Ledger's guidance specifically says to keep hardware-wallet recovery words offline, even when an online copy would be encrypted.

Follow your wallet manufacturer's backup instructions. Use a protected physical backup, such as paper or a suitable metal medium, and keep it away from theft, fire and water. Check accuracy privately. Do not paste the words into a website to check them or invent a scheme for splitting them. Store any additional recovery passphrase according to the wallet's instructions, separately where appropriate.

Lost access and suspected exposure need different responses

A missing backup does not always mean a lost wallet if an existing device still works. Do not reset or uninstall it impulsively. Follow the official wallet's process for establishing a new, independently backed-up wallet on a trusted device and, where possible, transferring remaining assets.

If a key or recovery phrase may have leaked, changing an app password or PIN does not invalidate that copied secret. Stop using the affected recovery setup and consult the wallet's official incident guidance. Recovery options depend on the wallet and what access remains; nobody can promise stolen funds back. Avoid unsolicited recovery helpers and never send them secrets.

Coordinate without surrendering control

Share only the nonsecret instructions needed for a payment or a family contact. Treat backup locations and account inventories as sensitive information too. A protected message cannot repair a compromised wallet, device or server, or erase a copy someone already made.

Official sources

Create Memo

Create Memo

Keywords

Bitcoin Wallet Safety: Share Addresses, Not Private Keys
Bitcoin
xpub
Bitcoin Wallet Safety: Share Addresses, Not Private Keys | LOCK.PUB