Why your Bitcoin receiving address changes

A fresh Bitcoin receiving address can still belong to the same wallet. Many self-custodial wallets offer new addresses to reduce address reuse. The change does not, by itself, replace your account or invalidate its earlier addresses. Verify the address in the intended wallet before sharing it.

This guide concerns Bitcoin Mainnet on-chain addresses in a self-custodial wallet, where you control the keys. An exchange’s deposit address follows that service’s current instructions. Lightning invoices and wrapped BTC are different cases.

One wallet can generate many receiving addresses

In a hierarchical deterministic (HD) wallet, keys and addresses come from a structured key hierarchy. The Receive screen can offer another address from that hierarchy while the wallet continues to manage the previous ones. The exact moment it offers a fresh address depends on the application; not every wallet changes it on the same click.

Bitcoin.org’s answer about changing addresses describes this normal behaviour. An address is a payment destination, not the name of your entire wallet. Generating one does not itself send a transaction, move existing BTC or require a network fee.

The reason for avoiding reuse is practical: payments to the same public address are easy to associate. A new destination reduces that direct connection. It does not make Bitcoin anonymous or prevent other transaction links. Bitcoin.org’s privacy guidance explains why public payment history still matters.

Does the old address still work?

For addresses generated by your own wallet, showing a newer address does not make the older one expire. For example, the Bitcoin.com Wallet documentation explicitly says it retains earlier addresses and can still receive payments to them.

The essential condition is that you still control the wallet that generated the address. An address copied from an old message does not prove that you still control it. Do not extend this rule to an exchange deposit address, a payment processor’s invoice, or someone else’s old payment instructions. Obtain current instructions from that recipient or service.

For a new payment to your own wallet, use its current verified receiving address. There is no need to move existing BTC just because the Receive screen changed. If a payment was already sent to a verified older address you still control, inspect that payment in the wallet instead of asking the sender to pay again.

Verify the next receiving address

1. Open the intended wallet and account. Choose Bitcoin Mainnet, then the account you mean to receive into. A second Bitcoin account or a different passphrase wallet can have its own addresses. A familiar account label alone is not an address check.
2. Get the address from Receive. Use the wallet’s normal receiving workflow. On a hardware wallet, display and verify the complete address on the device. Trezor’s receiving instructions describe its Verify step; other products have their own controls.
3. Check the pasted destination. When sending from another application, check that it also uses Bitcoin Mainnet and compare its full pasted address with the verified one before approving the payment. If you are sharing an address with a payer, check the full address you send them. Do not rely on a matching beginning and end. If the values disagree, stop and investigate through the wallet’s official support route.
4. Keep the payment tied to that address. Once sent, use the transaction ID to check that the transaction pays the address you verified, and view the payment in your wallet. A later change on the Receive screen is not evidence that the payment went elsewhere.

You do not need to disclose a seed phrase or private key, sign a transaction, or transfer BTC merely to check a receiving address. A transaction you choose to send afterwards is a separate action.

What happens to an address saved in a tracker?

A tracker limited to one address keeps watching that address when your wallet shows a new one. It does not automatically include the wallet’s other addresses, so a payment to the new address may appear in your wallet but be absent from the tracker.

In Owlio 1.1.0, checked on 5 November 2026, you add individual Bitcoin addresses. Owlio does not import an extended public key or derive the account’s other receiving and change addresses. If you add another verified address, it is another tracked entry; changing your wallet’s Receive screen does not update the earlier entry into a whole-wallet view.

Use the multiple-address guide for managing that list. When the question is about confirmation state rather than a new receiving address, use the separate confirmed and pending Bitcoin balance guide.

Owlio requests Bitcoin data from Blockstream, with mempool.space configured as a fallback. The queried service receives the address and can see your IP, as described in the privacy policy. Keeping the address list locally does not make these lookups invisible to the provider.

Would an xpub show the whole wallet?

An extended public key (xpub) lets a compatible viewing application derive a set of public keys and addresses without receiving the private keys needed to spend. It reveals more related activity than one receiving address. Treat it as sensitive viewing information, even though the xpub alone cannot spend your BTC.

Its scope matters. An account-level xpub is not a universal export of every account, address type or passphrase wallet. Trezor’s account guide distinguishes accounts and their own public keys. The Bitcoin wallet guide explains why an extended public key cannot derive hardened descendants.

A receiving-branch export also does not establish coverage of change addresses. The viewing tool must support the intended network, account type, export and branches. Address discovery has limits too: BIP 44 describes a scan stopping after a run of unused addresses. A partial or zero imported view is therefore not, on its own, proof that the entire wallet is empty.

You do not need to upload an xpub to understand why an address changed. For this check, the useful result is a verified receiving address for the intended account, plus a clear record of what your tracker actually watches.