
Most people don't think about deposit addresses once the swap is done. But the way an exchange handles the address after the coins are gone is a strong signal of how it treats your privacy.
One order, one address, forever
When you open a swap on Mistex, the system generates a brand-new address specifically for that order — derived from an HD-wallet tree for ETH-like coins, or allocated straight from a blockchain node for BTC/LTC, or a fresh subaddress from a Monero wallet. That address is written into the order row in the database and is tied to your order by its short ID.
Once the order reaches a terminal state — completed, expired, or refunded — the address is not released back into any pool. It stays bound to its original order forever. No future order will ever receive a deposit on that address.
Why not pool addresses?
Pooling deposit addresses is a common optimization in exchanges. It saves on RPC calls, keeps wallet trees small, and is operationally cheaper. But it bleeds privacy in two ways:
- Address clustering. A chain-analysis firm that sees two different deposits on the same address, months apart, will assume a single operator controls that address and group everything that ever flowed through it into one cluster.
- Cross-user linkage. Two unrelated users who happened to receive the same recycled address get their transaction graphs linked. Your swap is now forensically associated with someone else's.
By refusing to reuse, we make each of our deposit addresses a single-use artifact. A clustering heuristic has nothing to chain together.
What we do with the address after
Nothing. We keep the row in the database because we might need it for refund edge cases — if a user sends a late deposit to an expired address, we need to know which order it was. Beyond that, the address is an inert record.
There is no sweep, no consolidation, no rolling of incoming coins into a hot wallet that handles other orders. The coins move from the deposit address into the swap that fills your order, and then out to your payout address. Nothing lingers, and nothing gets mixed with other orders' funds.
What you can verify
Try it. Create a test swap, copy the deposit address, then try to create another swap and see if the address is ever the same. It won't be — not across minutes, not across years.
Takeaway
Address permanence is a tiny architectural choice that most users never see, but it's a load-bearing one for the privacy story. Pooling is cheaper; we chose the expensive option because it keeps your order graph disconnected from everyone else's.
If your exchange ever hands you a deposit address that looks like one you've seen before, you've been clustered.