Your Wallet Address Changed — Is the Old One Still Safe to Use?

An old crypto address is not automatically invalid just because your wallet now shows a different one. Bitcoin-style self-custody wallets commonly rotate receiving addresses for privacy while keeping the old addresses under the same wallet. But a different recovery phrase, a different wallet account, a network change or a custodial exchange can produce a very different answer. Before reusing any old address, prove who still controls it and whether the receiving service still supports it.

The short answer depends on who controls the old address

If the old address belongs to the same self-custody wallet and the current wallet can still derive or verify it, it can remain a valid receiving destination. If it belongs to a custodial exchange or service, the provider decides whether the old deposit address remains credited. If your current wallet was created from a different recovery phrase or account, the old address may still exist on-chain while no longer being controlled by the wallet you are looking at.

Use the Old Address Ownership Test

Do not send until all five proofs agree.

• Controller — is this a self-custody address controlled by your keys, or an address assigned by a custodian?
• Change reason — did the wallet rotate the receive address, did you switch accounts, restore a wallet, change network, or did a service replace a deposit address?
• Network — does the old address belong to the exact blockchain you intend to use?
• Current status — does the wallet or custodian still show the address as owned, associated, used, valid or otherwise supported?
• Receive proof — when appropriate, can a smallest practical test be received and controlled without violating a provider warning or minimum?

Case 1 — a Bitcoin wallet generated a fresh receive address

This is often normal behavior, not a sign that the old address was deleted. Ledger's current documentation says Bitcoin and several Bitcoin-based assets generate a new receiving address after receiving a transaction. Ledger keeps track of the previous addresses and states that those previous addresses remain valid.

Why Bitcoin wallets rotate addresses

Bitcoin transactions are public. Bitcoin.org recommends using a new receiving address for each payment to reduce linkability between payments, and Ledger explains that its new-address behavior exists for privacy. The new address is therefore often a recommendation for the next payment, not a revocation of the previous destination.

Valid does not mean optimal to reuse

An old Bitcoin address can remain technically valid while being a worse privacy choice. Reusing it ties additional incoming payments to the same visible address history. If you can easily give the sender a fresh verified address, that is usually the better privacy practice even though the old one still works.

Ledger gives a clear self-custody example

As checked on August 8, 2026, Ledger says its Bitcoin, Litecoin, Bitcoin Cash, Zcash and similar receiving addresses can change after a receipt while previous addresses remain valid. It contrasts these with assets such as Ethereum, XRP and Stellar, where the displayed account address normally stays the same.

A fresh UTXO address still belongs to the same account only if the wallet derives it

Hierarchical deterministic wallets can derive many receiving addresses from one wallet hierarchy. That relationship is what matters. Do not assume that two Bitcoin addresses belong to the same wallet merely because they appeared on the same computer at different times. Verify through the wallet's own address history or trusted device.

Hardware-wallet users should verify ownership on the device

Trezor's current receiving guide tells users to display and compare the receive address on the hardware wallet itself. The device screen is stronger ownership evidence than an old screenshot or clipboard entry on a computer that could have been replaced or compromised.

Case 2 — your Ethereum or EVM address changed

A normal externally owned Ethereum account does not rotate its address merely because it received a payment. Ethereum documentation derives the account address from its key pair, and MetaMask states that an account restored from the same private key remains at the same deterministic address. A changed EVM address is therefore a reason to check which account or recovery source you are viewing.

A different MetaMask account can look like the wallet changed its address

MetaMask can contain multiple accounts under one Secret Recovery Phrase. After restoration, not every previously created or imported account necessarily appears immediately. MetaMask's current documentation says derived accounts can be re-added in their original order, while accounts imported by private key, JSON or a different hardware wallet must be added again separately.

If the correct EVM account is restored, its address should match

MetaMask explicitly says addresses are derived deterministically from the private key and will be the same when the correct account is restored. If the address remains different, investigate account index, imported-account status, hardware-wallet connection or the recovery phrase used rather than treating the old address as superseded.

A new recovery phrase creates a different control boundary

If you set up a new wallet with a new recovery phrase instead of restoring the original one, the old address does not migrate into the new wallet merely because the application name is the same. Funds sent to the old self-custody address remain controlled by the keys that originally created it. Do not reuse that address unless you still possess and can securely access the original wallet authority.

Wallet application name is not ownership proof

Reinstalling the same application, buying a replacement hardware wallet or moving from mobile to desktop does not by itself prove that the same keys were restored. The old address belongs to cryptographic keys or a smart-account control system, not to the brand name of the app.

Case 3 — an exchange changed your crypto deposit address

Custodial deposit addresses require a different rule. The exchange controls the keys and its internal crediting system. You cannot prove continued creditability from the blockchain alone. Check the provider's current address-management policy before reusing an old deposit address.

Coinbase Exchange currently keeps old generated addresses associated

Coinbase Exchange currently says deposit addresses change for most assets when new addresses are generated, but all previously generated addresses remain associated with the account. Its help center says funds sent to an old generated address are processed and credited automatically to the corresponding wallet in the default portfolio.

Coinbase still recommends a current or unique address

The fact that Coinbase Exchange keeps prior addresses associated does not mean every exchange follows the same policy. Coinbase itself recommends documenting generated addresses and supports checking them in the account. For a new transfer, obtaining the current deposit details remains the simplest way to reduce ambiguity.

Kraken proves that some old crypto deposit addresses really can expire

Kraken's current crypto-address policy says an address may be set to expire when more than five addresses are generated for the same cryptocurrency or when an address type or format is no longer supported. Kraken tells users to stop using an address marked for expiry and warns that deposits to an expired address are not guaranteed to be credited.

An exchange logo cannot tell you whether an old address is reusable

Coinbase and Kraken currently have different documented behaviors. That is why no universal article should claim that exchange deposit addresses either always remain valid or always expire. The provider's authenticated deposit screen and current support policy are the source of truth.

Do not test an address that the exchange explicitly marks expired

A small test is useful when the status is uncertain but the platform still identifies the address as associated or valid. It is not a reason to ignore an explicit expiry warning. Kraken, for example, states that deposits to an expired address are not guaranteed to be credited and may be permanently lost.

Case 4 — the address changed because you changed networks

Some wallets show the same address text across several EVM-compatible networks, while other ecosystems use visibly different formats or accounts. A receiving address must be evaluated together with the network. The fact that an old string belongs to you on one network does not prove that the intended asset should be sent through another network.

Same characters do not merge balances across networks

An Ethereum-style 0x account can be visible on Ethereum, Base, BNB Smart Chain and other EVM networks. Those networks maintain separate state and asset balances. When the question is whether an old address can still receive, verify the sending network as part of the ownership test instead of comparing only the characters.

Case 5 — the old address came from a screenshot, note or withdrawal whitelist

A saved address is historical evidence, not current ownership proof. Before sending again, trace it back to the wallet or custodian that controls it today. This matters after wallet restores, device replacements, exchange migrations and address-book edits.

Do not verify an old address from transaction history alone

Transaction history can contain addresses you sent to, received from or encountered through address-poisoning attempts. Reconstruct the destination from the receiving wallet, a hardware-wallet display, the wallet's address list or the authenticated exchange deposit page rather than assuming a historical entry is still your destination.

A block explorer proves existence, not control

An explorer can show that the old address exists and received funds, but it cannot prove that your current wallet has the private key or that a custodial platform will still credit future deposits to it. Use the explorer as transaction evidence, not as the final reuse decision.

When a smallest practical receive test makes sense

Use a test only after ownership and network compatibility are already plausible. For self-custody, the test should be large enough to be economically usable after fees. For a custodial destination, it must meet the current deposit minimum. Never use a test to challenge an explicit provider warning that the address is expired or unsupported.

A successful test proves one route at one time

If the old address receives and you can control or see the credited funds, you have evidence that the route worked at that moment. It does not override future exchange policy changes, wallet migrations or privacy concerns. For recurring payments, periodically re-check the receiving destination.

Do not publish one old Bitcoin address forever just because it works

For a donation page or faucet payout profile, address reuse may be operationally convenient, but it links incoming payments publicly. Bitcoin.org recommends new receiving addresses for privacy. When the sender supports updating the destination without risk, a fresh verified address is preferable.

Do not replace a known-good address with an unverified new one

Address rotation should not create urgency. If a new address appears unexpectedly, verify it through the receiving wallet or hardware device before updating a withdrawal whitelist or recurring payout. Malware can also replace displayed or pasted addresses, so 'newer' is not automatically 'safer'.

Use five final verdicts

Finish the check with one explicit result.

• VALID, USE FRESH FOR PRIVACY — the old self-custody UTXO address remains controlled, but a new address is preferable for privacy.
• VALID BY PROVIDER POLICY — the custodian explicitly keeps the old address associated and current network rules still match.
• DO NOT REUSE — the custodian marks the address expired, retired or unsupported.
• DIFFERENT WALLET AUTHORITY — the current wallet uses different keys, seed, account or imported-wallet source; restore the original authority before using the old address.
• NETWORK MISMATCH — the address text may be familiar, but the intended asset/network route is not the one that produced or supports the old destination.

The safe old-address procedure

Use this sequence before sending real value.

• 1. Identify whether the destination is self-custody or custodial.
• 2. Record the exact asset and blockchain network.
• 3. Determine why a new address appeared.
• 4. For self-custody, verify that the old address is still derived, listed or confirmed by the wallet or hardware device.
• 5. For an exchange, read the current address status in the authenticated deposit interface and provider documentation.
• 6. Stop immediately if the provider marks the old address expired or unsupported.
• 7. If reuse remains valid, prefer a current fresh address when privacy or operational clarity matters.
• 8. Use a smallest practical test only when it is compatible with current minimums and no expiry warning exists.

Why this page is separate from the wallet-address basics guide

The existing wallet-address guide teaches how to build a correct receiving destination from asset, network, address, memo and ownership. This page starts later: the user already had a working destination, now sees a different address, and must decide whether the historical one remains under the same control or support policy.

Why this page does not become an exchange-deposit recovery guide

The decision before sending is simple: if a custodial address is expired or its status cannot be verified, use the current deposit details instead. Recovery after funds have already been sent to an expired exchange address is a different incident involving transaction evidence and provider-specific crediting rules.

What can change after August 8, 2026

Self-custody key relationships are durable, but wallet interfaces and custodial address-retention policies can change. Coinbase Exchange currently keeps prior generated crypto addresses associated, while Kraken currently supports explicit crypto deposit-address expiry. Re-check the receiving service before reusing an old custodial destination.

Sources checked on August 8, 2026

Primary wallet, protocol and exchange documentation was prioritized to separate cryptographic control from provider-specific deposit policy.

• Ledger Support — Receiving address changed — https://support.ledger.com/article/360034336713-zd
• Bitcoin.org — Protect your privacy — https://bitcoin.org/en/protect-your-privacy
• Trezor — Receive crypto in Trezor Suite — https://trezor.io/guides/sending-receiving-staking-funds/sending-receiving/receive-crypto-in-trezor-suite
• Trezor — Where are my coins stored? How Bitcoin wallets actually work — https://trezor.io/learn/basics/where-are-my-coins-stored-how-bitcoin-wallets-actually-work
• Ethereum.org — Ethereum accounts — https://ethereum.org/developers/docs/accounts
• MetaMask — Add missing accounts after restoring with Secret Recovery Phrase — https://support.metamask.io/configure/accounts/how-to-add-missing-accounts-after-restoring-with-secret-recovery-phrase/
• Coinbase Exchange — Why did my crypto address change? — https://help.coinbase.com/en/exchange/managing-my-account/crypto-address-change
• Coinbase Exchange — Generating new deposit addresses — https://help.coinbase.com/en/exchange/crypto-transfers/generating-new-deposit-addresses
• Kraken — Cryptocurrency deposit address expiry — https://support.kraken.com/articles/201647713-cryptocurrency-deposit-address-expiry

FAQ