I was recently asked for help with a Bitcoin withdrawal that never arrived. The person had withdrawn from Coinbase, the transaction looked like it had gone through on Coinbase’s side, but the coins did not show up in their Ledger wallet.
The mistake was easy to make: they opened an old Coinbase withdrawal in Ledger Live, copied what they believed was their receive address, and gave that address back to Coinbase as the destination for a new withdrawal.
Watch the video if you want to see this walkthrough with screenshots. But below is the written version, because this is one of those mistakes that can cost people real money when they are in a hurry.
The mistake: copying an address from an old transaction
A lot of people understand that receiving Bitcoin on a hardware wallet should involve checking the receive address carefully. But sometimes it feels annoying to unlock your Ledger every time you want to send someone your deposit address.
So what happens instead? You might think: “I already have a previous transaction in Ledger Live where I received funds from Coinbase. I’ll just open that old withdrawal, copy the first address I see, and use that.”
That is exactly what happened here.
The person found an old Coinbase withdrawal in Ledger Live. They saw a list of addresses under the transaction details. They copied the first one. Then they used it as the recipient address when withdrawing from Coinbase again.
The problem? That address was not their Ledger receive address. It was Coinbase’s change address.

Why the funds did not arrive on their Ledger
When you send Bitcoin, the transaction can have more than one output. One output may go to the person receiving the coins. Another output may be change sent back to the sender’s wallet.
In this case, the old Coinbase withdrawal had multiple outputs. The first address in the list was not the user’s Ledger address. It was an address controlled by Coinbase, specifically a change address.
So when they used that address as the recipient for their new withdrawal, they were not sending Bitcoin to their own wallet. They were effectively sending it back to Coinbase, but to an address that was not tied to their account in the way they expected.
From their point of view, the withdrawal had happened. From the blockchain’s point of view, the coins went somewhere else entirely.

The end result was frustrating: their funds were not in their Ledger. They had to contact Coinbase and go through several weeks of back-and-forth emails before the coins were credited back into their account.
That is a bad outcome that does not need to happen.
Bitcoin transactions can have multiple outputs
A common mental model for Bitcoin payments is: one sender, one receiver, one address. But real Bitcoin transactions are more flexible than that.
A transaction can have one output. It can have two outputs. It can have many outputs. In the same way that an email can be sent to multiple recipients, a Bitcoin transaction can send value to multiple addresses.
That means when you look at a confirmed transaction, the list of “to” addresses is not automatically a list where your address comes first. The order does not guarantee ownership. The first output may belong to you. It may belong to the sender. It may be change. Without more context, it can be hard to tell just from the raw list.

This is where people get into trouble. They assume that because they are looking at an old withdrawal from Coinbase to their Ledger, the first address in the list must be their Ledger address. That assumption is not safe.
What Ledger Live shows — and what it does not make obvious
To be fair, Ledger Live does include a “Why multiple addresses?” link when you see more than one output in an operation detail view. If you click that link, it takes you to Ledger’s documentation explaining change addresses.
The explanation is useful. It tells you that Bitcoin transactions can include a recipient address and a change address belonging to the sender’s wallet. That is exactly the concept at play here.

However, in practice, it does not always make it obvious which output belongs to you. You may need to read the explanation carefully and understand how change works before that detail clicks. For people who are new to Bitcoin transactions, or for anyone just skimming a screen while trying to receive funds quickly, this can be an easy thing to miss.

This is not meant as a criticism of Ledger. Different wallets make different design choices. But if you are relying on a wallet interface to tell you which address is yours, it helps to know whether that wallet actually makes that distinction clear.
How Electrum and Trezor handle this differently
When I compare the same transaction in other wallets, the difference becomes useful to see.
In Electrum, when you open the same transaction history, your own address can be highlighted in green. That is a small visual detail, but it matters because it helps you quickly distinguish an output that belongs to your wallet from outputs that belong to someone else or represent change.

Trezor also shows useful information in the transaction summary, including the receiving address used for the funds. Again, this is not about one wallet being “better” than another. It is about understanding that wallets do not all present transaction outputs in the same way.
If you are copying addresses from old transactions, you need to know whether your wallet is clearly identifying which output belongs to you. If it does not make that obvious, you should slow down and verify more carefully.
What block explorers can and cannot tell you
You might also look at a transaction in a block explorer. Block explorers show the inputs and outputs of a Bitcoin transaction. They are great for confirming that a payment happened, checking confirmations, and inspecting addresses.
But when it comes to identifying which output was yours versus which output belongs to the sender or is change, block explorers generally do not give you a simple label saying “this one is your address.” You may be able to figure it out with careful analysis, but that is not always quick or easy.
This matters because people often assume that if they can see multiple addresses in an explorer, one of them must obviously be theirs. It does not work like that. The blockchain shows the transaction structure; it does not necessarily explain your personal relationship to each output in a friendly interface.
What to do if you send funds to someone else’s change address
If you find yourself in this situation — you sent funds to what you thought was your receive address, but it turns out to be someone else’s change address — the first step is usually to contact the person or exchange that sent the funds.
In the case from the video, the user contacted Coinbase. After some frustrating back-and-forth, the funds were eventually credited back into their account. That is a good outcome, but it was not immediate, and it required patience.
There is an important caveat: proving that an address belongs to someone else’s change pool can require fairly detailed transaction analysis. It may not be enough to simply say, “That address looks like Coinbase’s.” You might need to show the relevant transactions and explain how the address relates to their wallet activity.
If you are dealing with a lost or stuck withdrawal and want help reviewing what happened before contacting an exchange or service provider, my recovery services consultations page is where I discuss that kind of support.
The safe habit: verify the receive address every time
The simplest and most reliable protection here is also the one people often skip in a hurry: verify the receive address on your hardware wallet before sending funds to it.
If you are receiving Bitcoin on a Ledger, do not rely only on what you see in Ledger Live. Do not copy an address from an old transaction and assume the first output is yours. Open the receive screen on the device itself, confirm the address there, and use that as your source of truth.
I know this adds a step. It means unlocking the hardware wallet. It means looking at the screen. But if you are receiving meaningful amounts of Bitcoin, that small extra step can save you from a very expensive mistake.
If you do not want to unlock your Ledger every time, there are other options too. You can use watch-only wallets on multiple devices to help verify addresses and reduce reliance on one desktop app. That can be useful for checking that the address you see is the one you expect, especially if you are worried about a compromised computer.
But even with those extra tools, the core habit remains the same: do not guess which output belongs to you. Verify it.
Practical checklist before giving someone your Bitcoin receive address
Here is what I would recommend doing each time you need to share a receive address for Bitcoin or another UTXO-style coin where change outputs are common.
-
Do not copy from an old transaction unless you understand the output list.
An old withdrawal may contain multiple addresses, including change addresses controlled by the sender. -
Check whether your wallet clearly highlights your own address.
Some wallets make this obvious. Others do not. If yours does not highlight it consistently, be extra careful. -
Verify the receive address on your hardware wallet screen.
This is especially important when receiving funds from an exchange or a third party. -
If you use watch-only wallets, use them to double-check consistency.
A second view can help confirm that the address you are about to share matches the one tied to your wallet. -
If something goes wrong, act quickly and document the transaction details.
Keep the transaction ID, addresses involved, timestamps, and any communication with the sender or exchange. -
Remember that “first output” does not mean “your output.”
This is the core mistake in this story, and it is easy to repeat if you are rushing.
Bottom line
Bitcoin transactions can have multiple outputs, and that creates a real risk when people copy addresses from old transaction details without understanding what they are looking at. In this case, the user copied what looked like their Ledger receive address from an old Coinbase withdrawal in Ledger Live, but it was actually Coinbase’s change address. The result was funds that did not arrive where expected and a long process to get them back.
The fix is simple: verify your receive address on your hardware wallet before sending anyone your deposit address. Do not assume the first address in a list belongs to you. Do not rely only on an old transaction view. And if your wallet does not clearly show which output is yours, slow down and check more carefully.
This is one of those security habits that feels minor until it saves you from losing funds to a simple copy-paste mistake.
Questions from viewers
Common questions from the comments on this video, with my answers.
I sent funds to an address that looked like mine but was actually the exchange's change address. Can I get them back?
If you sent funds to an internal exchange address (like a change address) instead of your deposit address, you will need to contact the exchange's support team. It is technically possible for them to recover it, but it depends entirely on their company policy and whether they are willing to take responsibility for the error. You may need to be persistent in your communication with them.
Why does my wallet balance look wrong or why can't I see my transaction immediately after sending?
If you are using full-node software like Bitcoin Core, you won't see a correct balance until the entire blockchain has fully synced, which can take several days. If you are using a lightweight wallet, the address might appear to 'change' because wallets often generate new addresses after a transaction uses the previous one. The funds might just be slow to reflect or waiting for confirmation.
I pasted an invalid address or made a typo. Did my money disappear?
No, if the address was invalid (for example, if you added random characters), the transaction would not have been accepted by the network. Bitcoin addresses are checksummed, so the software should reject the send. Your funds remain in your wallet, and you won't find the transaction on any blockchain explorer because it never left your device.
How do I know which output in a transaction belongs to me versus the change?
Bitcoin transactions can have multiple outputs. The first output is not guaranteed to be yours; the second is often the change returned to your own wallet. Some wallets like Electrum highlight your specific address, while others like Ledger Live may not consistently identify it. To be safe, verify the receive address directly on the hardware wallet screen or use a watch-only wallet to track which addresses belong to you.
Can I reuse my wallet address for multiple deposits?
Yes, you can reuse addresses as much as you like. It is not unsafe in terms of security, but it is not great for privacy because it links those transactions together. For most users, this is a minor trade-off, but if privacy is a concern, using a new address for each deposit is better practice.
I sent funds to the wrong network or token standard. Is recovery possible?
It depends on the specific assets involved. For some networks like Binance Smart Chain, there are straightforward recovery procedures if you follow the right steps. However, if you sent funds to a custodial wallet or exchange on the wrong chain, your only option is to contact their support and hope they help. Technical possibility doesn't always mean they will comply with your request. (Apps and tools change, so check the current version if something looks different.)
Stuck with a wallet recovery?
I maintain BTCRecover and have helped people recover seed phrases, passphrases and wallet passwords since 2019. Book a one-hour video session and I’ll walk you through doing the recovery yourself, without sharing your seed. Or, if you’d rather I run it, a trusted recovery is charged only if it succeeds.
Private sessions: US$100 per hour. Trusted recovery: 10% of recovered funds. I never contact people first and will never ask for your seed phrase over chat or email.
Found this useful?
These guides are free and ad-free. You can support them by sharing them, subscribing on YouTube, or sending a tip.







