Exchange Deposit Freezes Caused By Tainted Incoming Funds
The deposit that doesn’t arrive
You send tokens from your wallet to your exchange deposit address. The transaction confirms on-chain. The exchange shows it as pending, then keeps showing it as pending. After a while, an email arrives: your deposit is under review, and the compliance team needs more information about the source of the funds.
For most people, the first reaction is confusion. The funds came from your own wallet. You didn’t do anything unusual. Maybe they’re a claimed airdrop, or proceeds from a swap, or stablecoins you’ve been moving between chains for months.
What’s usually happened is that the exchange looked further back than your wallet. Somewhere upstream, in the history of the tokens you sent or the addresses that sent them to you, its screening system found a connection to something it’s required to be careful about: a sanctioned address, a known exploit, a mixer, a scam or a darknet market. The connection might be direct or several steps removed. It might be significant or trivial. Either way, it was enough to trigger a hold.
This piece explains how that screening works, why funds with a messy history upstream can cause problems even when you did nothing wrong, what the review process tends to look like and what helps it go smoothly. It covers deposits into exchanges, which is the opposite direction from the withdrawal linking and exchange choice pieces elsewhere on this site.
One thing up front, because this site takes it seriously. Nothing here is about getting flagged funds past a compliance check. Exchanges screen deposits because the law requires them to, and trying to disguise where funds came from is a much bigger problem than a delayed deposit. The aim is to understand the process, avoid accidental exposure and document your own activity so that a legitimate review is quick.
Why exchanges screen deposits at all
Regulated exchanges operate under anti-money-laundering and sanctions rules broadly similar to those that apply to banks. They’re required to know their customers, monitor transactions and avoid handling funds connected to sanctioned parties or serious crime. If they fail, they can face fines, lose licences or face criminal liability.
On-chain, this is both easier and harder than in banking. Easier, because every transaction is public, and the history of funds can be traced. Harder, because anyone can send anything to any address, and funds move through contracts, pools and bridges that mix sources together.
So exchanges use blockchain analytics providers. These firms build large databases of labelled addresses: exchanges, services, known scams, hack proceeds, sanctioned entities, mixers and so on. They cluster addresses believed to be controlled by the same party. And they provide screening tools that assess how an incoming transaction relates to those labels.
When a deposit arrives, the exchange’s system typically asks the analytics tool to score it. The score considers where the funds came from, how closely they connect to risky categories and how much value is involved. Based on that score and the exchange’s own policies, the deposit is credited normally, credited but flagged for review, or held pending review.
This happens automatically, usually within seconds of confirmation. You don’t see it unless something is flagged.
How screening looks upstream
The core question a screening tool asks is: how exposed is this deposit to risky sources?
Direct exposure is the simplest case. If the address sending funds to the exchange is itself labelled as a sanctioned entity, a known scammer or a hack wallet, the deposit is directly exposed. That’s almost always held.
Indirect exposure is where most confusion comes from. The sending address might be clean, but it received funds from somewhere that received funds from somewhere that is labelled. Screening tools can trace this back through a number of steps, often called hops, and estimate how much of the deposit’s value can be attributed to the risky source.
The way that attribution works varies by provider and by the method they use. Some approaches assume funds mix proportionally when they combine in an address. Others follow specific amounts through the chain. The details matter less than the principle: value can carry an association with its origin through several transactions.
Exchanges set thresholds on this. A tiny fraction of exposure several hops back might be ignored. A large share of exposure, or exposure to a severe category like sanctions, might trigger a hold even at a distance. The exact thresholds aren’t public, and they differ between exchanges and between jurisdictions.
Services in between complicate the picture. If funds pass through a large exchange, a big liquidity pool or a bridge, the trail often gets treated differently, because those services combine funds from huge numbers of users. Analytics tools have ways to handle these intermediaries, but they can still produce results that surprise people.
Why the same funds can score differently
People are often puzzled when one exchange accepts a deposit that another holds, or when a deposit that went through last month is held this month. The reason is that screening involves several choices, and different tools and exchanges make them differently.
The first choice is how to attribute value when funds mix. Imagine an address that holds 90 units from a clean source and 10 units from a labelled one, and then sends 50 units onward. Did that 50 carry a tenth of the risky association, all of it, or none of it? Analysts have names for different answers. A proportional or “haircut” approach assigns each outgoing payment the same mix as the balance, so the 50 carries a tenth. A “poison” approach treats any contact as full contamination, so the 50 is entirely flagged. Order-based approaches, such as first-in-first-out, follow specific units through in sequence. Each gives different results, and real tools often combine methods or use their own variants.
The second choice is how far back to look. More hops catch more distant connections but also more noise, since almost any address is connected to something risky if you go back far enough.
The third is how to treat large intermediaries. Big exchanges, liquidity pools and bridges combine funds from huge numbers of users. Tools usually stop tracing through them, or treat them in a special way, because otherwise almost everything would appear exposed to almost everything.
The fourth is timing. Labels are added as analysts discover new information. An address that was unlabelled when you received funds from it may be labelled later, and a deposit screened today may score differently from an identical one last month.
And the fifth is each exchange’s own policy. Two exchanges using the same analytics provider can still set different thresholds for what counts as a hold.
None of this is visible to you as a user. It’s worth knowing about mainly because a hold is the result of choices you can’t see, applied to history you can partly check, which makes it feel less arbitrary.
The categories that trigger holds
Not all risky categories are treated the same. Some almost always result in a hold, and some depend on scale and distance.
Sanctions are the strictest. Addresses associated with sanctioned individuals, entities or services are treated very seriously in many jurisdictions. Exchanges often have little discretion here, and exposure even at some distance can cause a hold.
Stolen funds from hacks and exploits are next. When a protocol is exploited, the attacker’s addresses are usually identified and labelled quickly, and the funds are tracked as they move. If those funds pass through pools, bridges or other users on their way somewhere, some of that association can travel with them.
Mixers and privacy services are treated as high risk by many exchanges, regardless of why someone used them. Funds that came out of a mixer, or passed through an address that used one, are commonly flagged.
Scams and fraud cover a range of labelled addresses, from drainer operators to fake investment schemes. If funds from a scam victim end up with you somehow, they can carry that label.
Darknet markets and other illicit services are labelled by most analytics providers.
High-risk exchanges or services in certain jurisdictions may also raise scores, depending on the exchange’s policies.
For most farmers, the realistic exposures are exploit proceeds, scam-related funds and, occasionally, mixer-related or sanctioned sources that reached them indirectly.
How farmers pick up exposure without noticing
People who farm airdrops rarely intend to receive tainted funds. But farming involves a lot of activity that touches many counterparties, and a few paths are common.
Peer-to-peer trades and OTC deals are one. If you buy stablecoins or tokens from an individual, you receive whatever history their funds carry. You have no way of seeing it in advance without checking.
Receiving from other people is another. Payments for services, shared costs within a group or funds from friends all bring their sender’s history with them.
Interacting with exploited protocols can do it too. If you claim or withdraw from a protocol shortly after an exploit, you may interact with contracts or pools whose balances have been affected by the attacker’s activity. Whether that creates meaningful exposure depends on how the analytics tool treats the protocol.
Unsolicited transfers can create exposure you never asked for. Anyone can send tokens to your address. There have been episodes where small amounts were sent from sanctioned services to many well-known addresses, apparently to make a point. Most exchanges treat tiny, unsolicited amounts differently from substantive activity, but it can still show up in screening.
Consolidating funds from many sources into one wallet before depositing can combine exposures. If one of ten sources has a problem, the combined deposit now carries part of that problem.
And bridging or swapping through services the analytics tool classifies as risky can add to a score, even when your own use was entirely ordinary.
None of these is wrongdoing. They’re the normal side effects of moving value in a public, interconnected system.
What a hold looks like
Holds vary between exchanges, but some patterns are common.
The deposit may show as pending, under review or on hold in your account. Sometimes the exchange credits it but restricts withdrawals from the account. Sometimes the whole account is restricted.
You’ll usually receive a message asking for information. This might be a questionnaire, a request for documents or an invitation to explain the funds in your own words. It generally asks where the funds came from, what the transactions were for and how you came to hold them.
Timelines aren’t guaranteed. Some reviews resolve within days. Others take weeks, especially if the exchange needs to escalate internally or if the exposure involves a severe category. Exchanges rarely give precise timelines, and pushing for one usually doesn’t help.
The possible outcomes include release, where the deposit is credited normally once the exchange is satisfied; continued restriction pending more information; closure of the account with funds returned in some form, subject to the exchange’s policies and legal obligations; or, in serious cases, the funds being frozen while authorities are involved.
What you won’t usually get is a detailed explanation of exactly which address triggered the hold. Exchanges typically don’t disclose their screening results or thresholds, partly for legal reasons and partly to avoid teaching people how to evade them.
Issuer freezes are a different thing
Exchange holds are often confused with a separate mechanism: freezes by the issuer of a token. They can look similar from the outside, but they involve different parties and different processes.
Some tokens, particularly fiat-backed stablecoins issued by companies, include functions in their contracts that let the issuer freeze specific addresses. A frozen address can’t send those tokens. Issuers typically use this in response to sanctions requirements, law enforcement requests or cases of confirmed theft.
An issuer freeze happens on-chain, at the token level. It doesn’t matter where the tokens are. If your wallet address is frozen by an issuer, you can’t move those tokens anywhere, and no exchange is involved.
An exchange hold happens off-chain, inside the exchange’s own systems. The tokens have already arrived at the exchange’s address. The exchange is deciding whether to credit them to your account.
The practical differences matter. If an exchange is holding your deposit, you deal with the exchange’s compliance team, and the outcome depends on its review. If an issuer has frozen an address, only the issuer can unfreeze it, usually through a formal process, and exchanges can’t override it.
Issuer freezes are generally aimed at addresses directly involved in a problem, such as an exploiter’s wallet, rather than at people several hops away. For most farmers, an issuer freeze on their own address is unlikely unless they received a lot of funds directly from a flagged source. But it’s worth knowing the power exists, and that some stablecoins carry it while others don’t.
It also means that tokens you hold can be affected by events you had nothing to do with. If a pool or protocol you’re using holds tokens at an address that gets frozen, your position there could be stuck even though your own wallet is fine.
Many wallets, one exchange account
Farms often send proceeds from many wallets into one exchange account. That has implications for reviews that are worth thinking through.
First, a review rarely looks at one deposit in isolation. If one deposit is held, the compliance team may look at the account’s other deposits, its withdrawal history and the wallets it interacts with. A question about one wallet can become a question about all of them.
Second, many wallets depositing into one account links those wallets from the exchange’s point of view. That’s a separate topic, covered in the pieces on withdrawal linking and consolidating after a claim. The relevant point here is that the exchange already knows those wallets feed the same account, so your explanation needs to cover them all consistently.
Third, one problematic wallet can affect the account. If one of your wallets received funds with significant exposure, depositing from it into your main account can put the whole account under review, not just that deposit.
This is another reason to keep funds from third parties and unknown sources separate, and to check before depositing from any wallet whose history you’re not sure of. It’s also a reason to keep your records organised per wallet, so you can explain each one’s funding and activity quickly.
None of this suggests hiding the relationship between your wallets and your account. The exchange knows who you are. The goal is simply to make sure every wallet feeding the account has a history you can explain.
What the compliance team is trying to learn
It helps to think about the review from the other side. The compliance analyst is trying to decide whether the exchange can accept these funds without breaking its obligations.
They want to understand the chain of custody: how the funds came to you, and whether you were plausibly unaware of any problem upstream.
They want to see whether your explanation matches the on-chain record. If you say the funds are proceeds from an airdrop claim, they’ll look for the claim transaction. If you say you bought them on another exchange, they’ll look for the withdrawal.
They want to assess whether the exposure is incidental or central. A small, distant connection in an otherwise clear history reads differently from funds that came largely from a labelled source.
They want to know whether you’re connected to the risky party. Someone who received exploit proceeds in a DEX trade is in a different position from someone who received them directly from the exploiter.
And they need to document their decision. Whatever they decide, they have to be able to justify it later.
Your job is to make that assessment easy with clear, accurate information.
Answering a source of funds request
When the request arrives, a calm, thorough answer usually works better than a quick, defensive one.
Answer every question asked. Partial answers usually lead to more questions and longer delays.
Explain the flow plainly. Something like: “These tokens were claimed from the protocol’s official claim contract on this date in this transaction, then swapped for stablecoins in this transaction, then sent to my deposit address in this transaction.” Include transaction hashes for each step.
Provide supporting documents where they exist: screenshots of the claim page, exchange withdrawal records from where you originally acquired funds, invoices or agreements if the funds were payment for something.
Be honest about what you don’t know. If you received funds from a peer-to-peer trade and don’t know the counterparty’s history, say so. Inventing a clean story that doesn’t match the chain is the fastest way to make things worse.
Keep your tone factual. Frustration is understandable, but it doesn’t speed anything up, and it can make an analyst more cautious.
Keep copies of everything you send and receive, with dates.
And follow up politely if you hear nothing for a long time, through the exchange’s official support channels only. During holds, people often get contacted by fake “compliance agents” offering to speed up the release for a fee. Real exchange compliance teams don’t do that.
If the review ends badly
Most reviews end with the deposit credited. Some don’t, and it’s worth knowing the less comfortable outcomes so they don’t come as a complete shock.
An exchange may decide it can’t accept the funds and close the account. What happens to the funds then depends on the exchange’s terms, its legal obligations and the nature of the exposure. Some exchanges allow withdrawal of the balance to an address you control. Some return funds to the sending address. In severe cases, especially involving sanctions or active investigations, funds may remain frozen while the exchange follows legal requirements.
An account closure after a compliance review isn’t necessarily a finding that you did anything wrong. It can simply mean the exchange decided the risk was outside its appetite. It still matters, because some exchanges share information with each other or with authorities in certain circumstances, and because it can be hard to reopen an account after closure.
If this happens, keep every piece of correspondence. Ask, politely, what options are available for the funds. Respond to any further requests accurately. If the amount is significant, get professional advice before taking further steps.
What you shouldn’t do is try to move the problem elsewhere, such as withdrawing funds and immediately depositing them at a different exchange through several extra hops. That can look like an attempt to avoid scrutiny, and it can make any future review much harder.
It’s also worth reflecting on how the exposure arose. If it came from a counterparty you didn’t know well, or from mixing third-party funds with your own, those are habits you can change.
Records that make reviews straightforward
The best time to prepare for a review is long before any deposit is held. Good records turn a stressful request into a copy-and-paste job.
Keep a record of where your funds come from. For each wallet, note how it was funded, with transaction hashes. For claims, note the protocol, the claim transaction and the date. For swaps and bridges, keep the hashes. For exchange withdrawals, keep the exchange’s own records.
Keep records of peer-to-peer or OTC trades, including who the counterparty was, what was exchanged and the transaction hash. If you don’t know enough about a counterparty to explain the trade later, that’s worth thinking about before trading.
Keep a note of anything unusual: unsolicited tokens you received, interactions with protocols that were later exploited, times you used services that might be classified as high-risk.
Many farmers already keep spreadsheets or use portfolio tools for tracking what they spent. Extending that to include the source of funds is a small step that pays off heavily if a deposit is ever held.
Records also help with things beyond exchange reviews, including your own accounting. How any of this should be treated for tax is a question for a qualified professional in your jurisdiction.
Checking before you deposit
You can’t see an exchange’s screening results in advance, but you can reduce surprises.
Look at the history of funds you received from other people before depositing them. A block explorer shows where incoming funds came from. You don’t need to trace everything, but a quick look at the last few steps can reveal an obvious problem, such as funds arriving from an address labelled as an exploiter.
Many explorers show labels on known addresses, including hack wallets and sanctioned entities. If you see one a step or two upstream of funds you’re about to deposit, that’s a signal.
Some analytics providers offer free tools for checking whether an address is on a sanctions list. They don’t give you the full risk score an exchange would see, but they catch the most serious category.
Keep funds from different sources separate where you reasonably can. If you received something from an unknown counterparty, holding it in its own wallet, rather than mixing it with your clean funds, means that if it causes a problem, it doesn’t take everything else with it.
And don’t treat hops as a cleaning process. Moving funds through extra wallets or services to put distance between them and a risky source is the kind of behaviour compliance systems are designed to detect, and it can turn an innocent exposure into something that looks deliberate.
The dust you never asked for
Unsolicited transfers deserve their own note, because they worry people more than they usually should, and they’re mishandled in ways that make them worse.
If a small amount arrives from an address you don’t recognise, and particularly one labelled as risky, don’t interact with it. Don’t send it back, don’t swap it and don’t move it along with your other funds.
Moving it combines it with your clean balance, which can spread its association to everything it’s mixed with. Leaving it where it is keeps it isolated.
Record that you received it, with the transaction hash and date, and note that it was unsolicited. If it ever comes up in a review, you’ll be able to say exactly what happened and show that you didn’t engage with it.
Exchanges generally understand that anyone can receive unsolicited funds. A tiny, unsolicited incoming transfer, left untouched, is treated very differently from actively receiving and using funds from a risky source. What matters is what you do with it.
If the amount is significant, or if you’re concerned, it’s reasonable to contact your exchange’s support proactively and explain, before depositing anything from that wallet.
A worked example
Here’s a made-up case to show the process.
A farmer claims an airdrop across several wallets and swaps the proceeds for stablecoins on a DEX. One wallet also received stablecoins from a friend who was repaying a shared cost. The farmer sends the stablecoins from that wallet to their exchange.
The deposit is held. The exchange asks for the source of funds.
Looking back, the farmer checks the friend’s transfer on the explorer. The friend’s address received those stablecoins from a P2P trade, and the counterparty in that trade received them, a few hops earlier, from an address now labelled as connected to an exploit.
The farmer answers the exchange’s questions: the airdrop claim, the swap and the friend’s repayment, each with transaction hashes and dates. They explain that the friend’s funds came from a trade they weren’t party to, and that they had no knowledge of the upstream exploit. They include a screenshot of the message where the friend confirmed the repayment.
After some days, the exchange credits the deposit, noting the indirect exposure. The farmer resolves to keep third-party funds in a separate wallet in future, and to check the last few hops before depositing anything that didn’t originate with them.
Nothing in this example was hidden or disguised. The review went smoothly because the records existed and the explanation matched the chain.
What people get wrong
Several common reactions to a hold make things harder.
Trying to cancel or redirect the deposit. Once funds are at the exchange’s address, they’re under the exchange’s control. There’s no reversing the transaction on-chain.
Sending more funds to “prove” legitimacy. It doesn’t help, and it can expand the review.
Opening accounts elsewhere to deposit the same funds. That can look like an attempt to avoid scrutiny, and exchanges may share information in some circumstances.
Using a “clean-up” service or extra hops before depositing. This is exactly what screening is designed to catch, and it turns an accidental exposure into apparent intent.
Assuming the exchange is being unreasonable. It may feel that way, but analysts are working under rules they don’t set. Clear information helps them clear your deposit.
Paying anyone who offers to “unlock” funds. Fake compliance agents and recovery services target people with held deposits.
Where this explanation stops
I want to be clear about the limits here. Screening methods, thresholds and policies differ between exchanges, analytics providers and jurisdictions, and they change over time. Nothing here tells you whether any particular deposit will be held, or how any exchange will decide a case.
I don’t have data on how often deposits are held or how long reviews take on average, and exchanges generally don’t publish it. Anyone quoting precise figures for this should be asked where they came from.
This is also not legal advice. If a hold involves a large amount, a severe category like sanctions, or a request from authorities, getting advice from a qualified professional in your jurisdiction is sensible.
What the mechanics make clear is that on-chain funds carry their history with them, exchanges are required to look at it, and the people whose reviews go smoothly are the ones who can explain their own history with records that match the chain.
For more on exchange risk, clean records and the habits that keep a farm’s funds moving without surprises, head back to the Airdrop Farming homepage.
Get new guides and videos first — join the Telegram channel.