← back to blog

What a Centralised Exchange Sees When You Withdraw

Most people running more than one wallet spend their effort on the wallet side. Different seed phrases, different browser profiles, maybe different devices. That’s the right instinct, but it skips the step where the whole setup usually gets tied back together: the moment funds leave a centralised exchange.

A wallet with no transaction history is anonymous in the sense that it isn’t linked to anything yet. The first transaction it ever makes is what gives it an identity. If that first transaction is a withdrawal from an exchange account that has your ID on file, the wallet now has a thread running straight back to you, and every other wallet funded the same way shares that thread. This is what “exchange withdrawal linking” actually means in practice, and it’s worth understanding mechanically rather than treating it as a vague privacy worry.

What the exchange itself records

When you withdraw, the exchange isn’t just moving coins. It’s writing a row to a database that ties together:

  • Your account ID and whatever KYC documents are attached to it
  • The withdrawal address and the network you sent it on
  • The amount, the fee, and the exact timestamp
  • The IP address and device fingerprint the withdrawal request came from
  • In many cases, a risk score assigned to the destination address before the withdrawal is even approved

That last point matters. Exchanges like Binance, Coinbase, and Kraken run every outbound address through a screening tool, usually Chainalysis KYT, TRM Labs, or Elliptic, before releasing funds. The screening isn’t just checking for OFAC sanctions. It’s pulling whatever cluster data those firms already hold on the address, so the exchange knows, before the transaction confirms, whether that address has ever touched a mixer, a known exchange hot wallet, or a wallet already flagged for bot-like behaviour.

None of this requires anything exotic on the exchange’s part. It’s a standard compliance stack that every major regulated exchange runs, because regulators require it under the same “know your customer” and anti-money-laundering rules that apply to banks. The Travel Rule adds another layer: for withdrawals over certain thresholds, exchanges are required to share originator and beneficiary information with the receiving exchange if the destination is also a regulated platform.

How chain analysis extends the picture after the withdrawal

Once the funds leave the exchange, the on-chain side takes over, and this is where clustering happens. The core technique chain analysis firms use is the common-input-ownership heuristic: if multiple addresses are used as inputs to the same transaction, they’re assumed to be controlled by the same entity, because you need the private key for each one to spend from it. That’s a Bitcoin-era idea, but the equivalent on account-based chains like Ethereum is simpler and often more reliable: if one address sends gas or seed funding to five other addresses, those five addresses get grouped into the same cluster as the funding source.

This is the part that catches people who otherwise did everything right on the wallet side. You can have five separate seed phrases, five separate browser fingerprints, five separate proxy exit IPs, and none of it matters if all five wallets received their very first ETH from the same exchange withdrawal address within the same hour. The funding transaction is the fingerprint. Chain analysis firms build exactly this kind of graph, and it’s not exotic detective work, it’s the first thing any clustering algorithm checks because it’s cheap and highly reliable.

A few specific patterns make the link even easier to draw:

  • Round, identical funding amounts sent to multiple wallets (0.05 ETH to each of ten addresses is a much stronger signal than ten different amounts)
  • Funding transactions clustered tightly in time, since a script or manual batch run tends to fire them within minutes of each other
  • Gas top-ups from the same source later on, when one wallet runs low and gets refilled from the same place the others were
  • Rewards or airdropped tokens later sent back to the same CEX deposit address to sell, which closes the loop even if the funding side was handled carefully

That last one is the most common mistake. People are careful about how they fund wallets and careless about how they cash out, and cashing out is exactly where the exchange’s own KYC data reconnects everything.

What happens once the wallets are already linked

For a chain analysis firm, once wallets are grouped into a cluster, that cluster gets treated as a single entity going forward. Every future action any of those wallets takes, including which airdrops they claim, gets attributed to the entity as a whole rather than to individual addresses. Projects doing snapshot and sybil analysis for their own airdrops use very similar clustering logic, and in some documented cases they’ve directly licensed or built on top of the same kind of common-funding-source heuristics that exchanges and analysis firms use for compliance. A wallet cluster that all funded from one address, interacted with the same protocols in the same order, and cashed out to the same exchange account is a textbook sybil signature, independent of whether any individual wallet looks suspicious on its own.

On the exchange side, if a deposit address is later found to be part of a cluster that touched something the exchange doesn’t want exposure to (a sanctioned entity, a mixer, a hack-related address), the exchange can freeze the deposit and ask for a source-of-funds explanation, even if the specific wallet depositing never directly touched anything illicit itself. The freeze happens because of cluster membership, not because of that wallet’s own history.

How operators actually structure funding to avoid this

None of this is about hiding from the exchange, your KYC’d account is always going to be the account that funded the wallets, and that’s not something to try to obscure. It’s about not making the graph trivial to build. A few practical habits:

  • Withdraw at different times, not in one batch. Space funding transactions out over days, not minutes.
  • Vary the amounts. Sending 0.043 ETH, then 0.071 ETH, then 0.028 ETH breaks the round-number pattern that makes clustering easy.
  • Use an intermediate hop, such as swapping through a DEX aggregator or bridging to a different chain, rather than sending straight from the exchange withdrawal address to every farming wallet.
  • Never top up gas across wallets from the same source once they’re already active. If one wallet needs more gas, fund it independently rather than drawing from a shared pot.
  • Route rewards to sell through more than one path over time rather than consolidating everything back into a single CEX deposit address the moment a token goes live.

This is defensive hygiene, the same category as not reusing the same proxy exit IP across every wallet session or not running every browser profile with identical fonts and screen resolution. It reduces the strength of the signal available to whoever is clustering, it doesn’t make the wallets untraceable, and it isn’t a way to break exchange terms of service or evade legitimate compliance checks. Exchanges are entitled to know who their customers are. The point of separating funding patterns is to avoid accidentally building one obvious cluster out of wallets that were meant to represent independent participation, which is the same standard a project’s own airdrop eligibility criteria usually expects anyway.

The bigger picture

Wallet separation only works as far as its weakest link, and for most people that link is the funding transaction, not the wallet itself. Understanding what an exchange logs and how chain analysis clusters addresses afterward is the difference between running multiple wallets as genuinely independent participants and running one entity with ten addresses that happen to look different on the surface.

For more breakdowns of how on-chain clustering works and tested reviews of the tools people use to run wallets, proxies, and browser profiles properly, head back to the Airdrop Farming homepage.

Get new guides and videos first — join the Telegram channel.

need infra for this today?