Counterparty risk
The service becomes a new debtor for the full swap amount. No-KYC removes identity checks, not insolvency, exit risk, or seizure of the service’s wallet.
A threat-model checklist for traders who want to see exactly where control, privacy, and recovery options shift before they click confirm.
13 min read
Sort a swap by one question: does your address still sign the release of funds, or does the service sign for you? That single fact sets most of the and the practical privacy and security trade-offs for anonymous trading. If the service signs, it has custody; if only your key can move the coins, you retain control.
Treat non-custody as the default for anonymous swaps. Custody adds counterparty risk but may reduce chain linkage when the service batches outputs or uses internal ledgers.
| Feature | Custodial no-KYC swap | Non-custodial no-KYC swap |
|---|---|---|
| ;; You sign the outgoing spend | no, service does | |
| ;; Service holds coins at any point | ✕ | |
| ;; Visible on-chain linkage from your address | often buffered by internal ledger | direct, unless mixed later |
| ;; Freeze or delay risk | service can halt | mostly absent, except contract/routing failure |
| ;; Recovery if service disappears | depends on support | you keep the key |
If the interface has a “withdraw” button for funds you just deposited, you are not holding the keys.
A non-custodial flow can still involve a temporary contract with an admin key. Ask who can pause or drain that contract before you call it non-custodial.
The practical privacy gain from custody is narrow: you replace an on-chain link with an internal database entry. The security loss is broad: you add a third party that can freeze, lose, or selectively report the flow.
In a custodial no-KYC swap you surrender two things at once: exclusive control of the private key for the deposit asset, and the ability to force settlement on-chain yourself. The swap window is the entire period from your outgoing transaction’s first confirmation until the incoming transaction to your withdrawal address is irreversible. During that window the service — not you — decides the destination, the timing, and whether the coins move at all.
The service becomes a new debtor for the full swap amount. No-KYC removes identity checks, not insolvency, exit risk, or seizure of the service’s wallet.
You hold an IOU inside the platform, not a UTXO you can spend. If the service pauses the coin, your asset is frozen with it.
You depend on the service’s support ledger, not on a seed phrase. A wrong memo, wrong network, or internal flag can make recovery manual or impossible.
The service sees the full pair: your deposit address, amount, requested asset, and withdrawal address — in one session. Decentralized swaps can split that view; custodial flows concentrate it.
A custodial no-KYC swap can still collect and store the full session: IP, browser fingerprint, deposit address, withdrawal address, amount, and time. “No KYC” limits identity documentation, not session correlation.
| Control factor | Non-custodial swap | Custodial no-KYC swap |
|---|---|---|
| Who holds the private key during the swap | you | the service ;; What you hold if the service stops |
A non-custodial swap keeps your private keys in your wallet at every stage: the service never receives a deposit address under its control. What gets “broken” is only the direct transfer link on the transparent chain, not the underlying address history. The swap’s privacy claim depends on how the two legs are matched — through liquidity pools, order books, or cross-chain protocols — and on whether any off-chain relay can correlate your sending address with the receiving address.
Non-custodial does not mean non-linkable. If you reuse the input or output address elsewhere, the swap leaves a cleaner chain trace than many custodial flows, but not an invisible one.
| Control point | Custodial no-KYC swap | Non-custodial swap |
|---|---|---|
| Who holds the private key during the swap | service wallet | your wallet ;; Freeze or seizure risk |
Treat the “break” as partial: the path is less obvious, not erased. Use a destination address you will not reuse for deposits tied to your known identity.
“No KYC” on a custodial service removes a named identity check, but it does not remove transaction observability. You avoid submitting a passport or selfie, while the service still builds a private record: your deposit address, swap route, amount, timestamp, and withdrawal address. Pseudonymity is not the same as unlinkability if one party holds the full session data.
The login-free flow creates the feeling of privacy because there is no username and no profile. In practice, the custodial engine can still record a temporary session, a browser fingerprint, an order ID, and the two wallet addresses it connected. Those data points are enough to link the incoming coins to the outgoing coins inside the service’s own database, even when no legal name was ever collected.
A custodial no-KYC swap is a data bottleneck. The operator sees the funding transaction before the swap and the departure transaction after it. If the two transfers occur within the same internal session, the link is trivial for the operator to reconstruct — regardless of what a public block explorer shows.
The ledger may be public, but the operator’s private order table is the sharper surveillance tool.
If the service later suffers a breach, receives a broad data request, or changes ownership, the stored session can become a retrospective identity source. Investigators may not need your name at swap time; they may combine the recorded deposit and withdrawal addresses with exchange withdrawal data, timing patterns, or IP logs obtained elsewhere.
Compare this with a self-custody flow: there is still a visible transaction on the chain, but no central database holds both endpoints of the swap as a single consumable record. In a custodial flow, the operator becomes the cheapest place to ask, because the mapping is already assembled.
Even a delete-my-data button does not prove that swap-time logs, backups, or analytics copies are also erased. Absence of KYC paperwork is not absence of a useful queryable record.
A non-custodial swap keeps your private keys with you at the moment of exchange, but the swap protocol, smart contract, or liquidity pool may still carry its own technical and counterparty risks. The main difference is that the largest single point of failure—a service holding your coins in a wallet it controls—is reduced or removed. You still need to review what you are signing and where funds are routed.
Yes. No-KYC usually means no passport or selfie at the start, but a custodial service can record wallet addresses, IP data, session logs, amounts, and timing. If that service is later compelled, breached, or changes its logging policy, the history may still be reconstructed or linked to an identity through other channels.
Custodial swaps can be useful when the other side of the trade is not easily available on-chain, when speed matters, or when a user does not want to manage transaction signing and gas timing themselves. In those cases the convenience or market access may feel worth the temporary loss of key control. The decision should be treated as a trade-off, not as a default.
Look at where your deposit is sent and who can move it after you send it. If the flow gives you a deposit address controlled by the service, then asks you to trust that the service will return the swapped funds, you are likely dealing with a custodial step. Non-custodial flows usually keep the exchange bound to your own wallet or to a contract where the release condition is visible in the transaction itself.
Refuse a custodial swap when the amount is large enough to become a seizure target, when the asset already has weak on-chain privacy, or when the service cannot prove segregated custody. Accept it as the lesser risk only for small, fast conversions where self-custody errors — wrong address, lost seed, failed broadcast — exceed the custodian’s default risk.
| Scenario | Refuse custodial | Consider custodial |
|---|---|---|
| Large amount | yes, self-custody plus a signed hardware wallet is safer | no, the counterparty risk now exceeds the UX risk ;; Privacy coin transition |
Set a hard amount: below it, custodial delay is acceptable; above it, split into non-custodial swaps with signed addresses only.
A custodial swap that feels private because there is no KYC is not private if the service logs IP, browser fingerprint, and deposit address together. Refuse it when the on-chain trail matters more than the login screen.
Recheck three things on a fixed schedule: custody behavior, address hygiene, and service-level changes that could invert your threat model. Run this list before any sizeable swap, at least once per quarter, and immediately after a service updates terms, liquidity routes, or interface flows.
A service that was non-custodial six months ago can become custodial after a router upgrade, an acquisition, or a liquidity migration. Recheck the deposit screen every time; do not rely on a label in an old comparison table.
For recurring swaps, keep a small log entry with date, route used, destination prefix, and observed delay. A later anomaly is much easier to spot against a remembered baseline.
Set two calendar reminders: a 30-day review for the services you actually use, and a full recheck after any major wallet or protocol update on your own side.