You paste an address, hit send, and a second later notice the last few characters do not match what you meant to copy. Or a friend tells you the address you sent to is not theirs. The transaction is already confirmed on Base, and now you are trying to figure out if the funds are gone for good.
This is a different problem from sending a token to the right address on the wrong network, which has its own article here. This one is about sending the right network but the wrong destination. The honest answer is that what happens next depends entirely on what kind of address received your funds, so the first step is understanding that, not panicking.
Why there is no undo button
Base, like every EVM network, does not have a concept of reversing a confirmed transaction. There is no bank to call, no chargeback process, and no central operator who can claim funds back on your behalf. A transaction that includes a valid destination address and enough gas will execute exactly as instructed, and once it is included in a block it is final. This is the same property that makes self custody powerful: nobody can freeze or reverse your transactions either, including you.
Given that, your options narrow down to three fairly different situations.
Situation one: the address exists but nobody can access it
Some addresses are mathematically valid but have no known private key, either because they were never generated through normal wallet software or because the one who generated them lost the key long ago. If your funds landed on an address like this, they are not destroyed in a technical sense. They still exist on-chain. But without the private key, nobody, including you, can sign a transaction to move them. For all practical purposes, this is the same as losing the funds permanently. There is no recovery process, because recovery would require breaking the same cryptography that protects every other wallet on the network.
Situation two: a valid address that someone else controls
If you sent to an address you can identify, for example a friend's wallet, an exchange deposit address, or a business you recognize, the funds are intact and under someone else's control. Here the only path forward is asking that person or that exchange to send them back, which depends entirely on their goodwill and is not something anyone can require of them.
If it is a centralized exchange, contact their support team, give them the transaction hash from a block explorer, and ask whether they can trace the deposit to an account and return it. Some exchanges will do this, especially if the amount is clearly an identifiable deposit. Many will not, particularly for small amounts or if their process does not support manual returns. This is worth trying, but temper expectations.
Situation three: a smart contract that cannot handle the asset
This is the case that catches out even experienced users. If you send a standard token to a smart contract address instead of a wallet address, for example the token's own contract address, a staking contract, or a liquidity pool contract that was not built to accept that specific deposit, the tokens can become permanently stuck. The contract has no code path to send them back out, because its logic was never written to expect or forward that particular transfer. The same risk applies to sending an NFT to a contract that does not implement the receiver function it expects, on some standards that transfer will simply fail and revert, which is actually the safer outcome, but on others it can succeed and leave the NFT unreachable.
Before assuming funds are stuck this way, look up the destination address on a block explorer. If it shows contract code rather than a plain account, that confirms what you are dealing with, and you can sometimes find out from the explorer's labels or verified source code whether that specific contract has any owner function capable of recovering misdirected tokens. Most do not.
What actually helps, going forward
Since there is no fix after the fact for most of these cases, the practical value here is in prevention.
Send a small test amount first when you are using a new address for the first time, especially for larger transfers. The few extra seconds and the small gas cost are cheap insurance.
Use your wallet's saved contacts or address book feature if it has one, so you are selecting a verified entry rather than retyping or pasting a string of characters each time.
Verify both the beginning and the end of an address after pasting it, not just a glance at the middle. This also helps against address poisoning and clipboard hijacking, where malware or a scam transaction is designed to make a lookalike address appear in your history or clipboard.
Where available, use a human-readable name like a Basename instead of a raw hex address for people and services you interact with often. A name is harder to mistype and easier to double-check than forty hexadecimal characters.
The bottom line
A wrong-address mistake on Base is almost always final, and the outcome depends on what was on the receiving end rather than anything you can do afterward. An address nobody controls means the funds are effectively gone. An address someone else controls means your only option is asking for it back. A contract that cannot forward the asset usually means it is stuck for good. None of this is reversible through any kind of support channel, which is exactly why double-checking before you confirm a transfer is the only reliable protection you have.