Chain hopping describes value moving across several blockchains in quick succession, typically through bridges or swap services. It is named as a pattern because rapid cross-network movement is one of the shapes that appears when someone is trying to put distance between funds and their origin — and also, routinely, when an ordinary user is chasing a cheaper fee or a supported deposit network. What it does not do is remove history: each leg is public, and screening reports the connection rather than losing it at the boundary.
Every hop leaves two records, one on the chain the value left and one on the chain it arrived on. That is true whether the crossing used a bridge, a swap service or an exchange account. The records are not linked by a shared identifier, but they are linked by amount, timing and the service's own on-chain footprint, which is what makes reconstruction possible.
The pattern is therefore not a hiding technique that works. It is a shape that makes a history longer to read and, for the person holding the funds at the end, harder to document.
No, and the reasoning is worth stating plainly because the question is asked constantly by people who are worried rather than by people who are hiding. Moving value from one network to another does not delete the transactions behind it; it adds transactions in front of them. A screening result that covers both networks reports what was there before the hop.
What changes for you is the paperwork. Each additional service in the path is another place where you hold no record and cannot produce one on request. If you received funds you are unsure about, the step that helps is documenting where they came from — not moving them again. In order:
Because a desk that reads one chain in isolation gets a partial answer and does not know it. Cross-chain coverage is what turns "the funds arrived from a bridge" into "the funds arrived from a bridge, and before that from this". For an exchanger accepting deposits on several networks, that is the difference between a file that survives a bank review and one that does not.
Screen the counterparty address before you accept — free in the Telegram bot, three checks a day, with 10 chains covered at full AML depth and 35+ networks screened.
Cross-chain movement is described in plain words among the decision drivers, and any category found on the far side — theft, a market cluster, sanctions, an unverified venue — is named as its own category rather than absorbed into a generic warning. The verdict word (CLEAN, LOW, MEDIUM, HIGH, CRITICAL) and the recommendation (Proceed, Caution, Review, Reject) sit beside them.
Desks reviewing multi-network deposits work the case in the workspace, where the result exports as a signed report showing the legs in order — the document a bank actually asks for. Plans are on the pricing page.
No. Each leg is a public transaction, and screening that covers both networks reports the connection. The pattern lengthens a history rather than removing one.
No. Users move between networks for fees, for a supported deposit network, or to reach a specific application. The finding matters in combination with what is on either side, not on its own.
Where the value originated, not what the last hop was. Keep your counterparty's details and your own check result, since those are the records that answer the actual question.
Also available in: · · ·
Sanctuary covers 10 chains at full AML depth and screens 35+ networks, so common cross-chain routes read as connected legs instead of separate, unexplained arrivals.
Send any wallet to the Telegram bot and get a verdict in seconds. Three checks a day, free, no signup. Desks that screen every deposit run it on plans from $199/mo.