Crypto Wallet Exposure: Trace Flagged Funds Hop by Hop

Crypto Wallet Exposure: Trace Flagged Funds Hop by Hop

TL;DR: A sanctions list check only catches the address that's on the list. An exposure check catches the next step: an address that received money which started at a sanctioned or exploit wallet, directly or through intermediate addresses. With the Crypto APIs AML API you get the flagged source, the number of hops, the tainted share and every transfer on the path, so you can hold a deposit and show your evidence.

Most dirty funds don't arrive at your deposit address straight from a sanctioned wallet. They pass through one or two fresh addresses first. You run a list lookup on the sender, it comes back clean, and you credit the deposit. That's the gap exposure analysis closes. It asks a different question: not "is this wallet on a list?" but "did this wallet receive money that started at one?"

Address screening vs exposure: what's the difference?

Address screening matches the address itself against sanctions lists and other flagged-address sources. In our AML API that's Verify Address. You get a risk band, a 0 to 100 risk score, risk categories and the sources behind them, with OFAC, UK, EU and UN sanctions in every check.

Exposure follows the money. We build the transfer graph outward from flagged addresses and record every address their funds reached. If your user's deposit address sits 2 hops downstream of a sanctioned wallet, you'll know, even though the address itself isn't on any list.

You need both. Screening tells you who the counterparty is. Exposure tells you where its money came from.

How we measure exposure

  • Hops. A hop is one transfer. Hop 1 means the address got funds directly from the flagged address. We trace sanctioned sources up to 3 hops and exploit sources up to 2.
  • Poison model for sanctions. Any contact with a sanctioned address counts in full. If a wallet took a single payment from one, its exposure share to that source is 100%.
  • Haircut model for everything else. For exploits and fraud, exposure is proportional to the tainted share of the sender's balance at the time. A sender holding 10 flagged tokens and 90 of its own passes on 10% taint with every payment.
  • No time window. Taint follows the funds whenever they moved. Each result carries timestamps, so you decide how old is too old.
  • Noise filtered out. We ignore transfers under roughly $1 and spoofed token transfers from address poisoning. Smart contracts and burn addresses don't carry exposure, because routers and token contracts touch everyone's funds.

Exposure also feeds the risk score. Verify Address raises the score and band when an address received flagged funds, and it never lowers them. Direct receipt from a sanctioned wallet can lift the score to 70, from an exploiter to 55. For a named exchange, bridge or mining pool the exposure part is capped at 30, because a pooled wallet mixes the funds of many users.

How do you check exposure with the API?

It's 3 calls. Each one takes your API key in the X-API-Key header.

1. Screen the address. GET /aml/addresses/{address} returns flags, attribution and a short exposure hint: the blockchains where the address received traceable flagged funds, and the highest share.

curl https://rest.cryptoapis.io/aml/addresses/0x2718...6330 \
  -H "X-API-Key: YOUR_API_KEY"

2. Get the breakdown per source. Get Address Exposure, GET /aml/exposure/{blockchain}/{address}, lists every flagged address the funds trace back to, most exposed first.

curl https://rest.cryptoapis.io/aml/exposure/ethereum/0x2718...6330 \
  -H "X-API-Key: YOUR_API_KEY"
{
  "isExposed": true,
  "maxExposureShare": "1",
  "roots": [
    {
      "rootAddress": "0x7f36...be1b",
      "model": "poison",
      "hop": 1,
      "exposureShare": "1",
      "proportionalShare": "0.244848",
      "proportionalReceived": [
        { "contract": "0xdac1...1ec7", "value": { "amount": "1224.24", "unit": "USDT" } }
      ],
      "firstTimestamp": 1516066029,
      "lastTimestamp": 1516066029,
      "routes": 1,
      "direction": "received"
    }
  ]
}

3. Pull the evidence. List Address Exposure Paths, GET /aml/exposure/{blockchain}/{address}/paths, returns each route as a chain of transfers from the flagged address to yours: transaction hash, sender, recipient, amount, tainted amount and timestamp. Pass a rootAddress from step 2 to see only that source. Routes come sorted by tainted share, 10 per page by default, with a startingAfter cursor for the next page.

curl "https://rest.cryptoapis.io/aml/exposure/ethereum/0x2718...6330/paths?rootAddress=0x7f36...be1b&limit=10" \
  -H "X-API-Key: YOUR_API_KEY"

That route list is what your compliance analyst attaches to the case file. Anyone can check those transactions on-chain, so the decision doesn't rest on a black-box score.

Where does exposure fit in a deposit flow?

  1. A Blockchain Events webhook tells you a transaction hit one of your deposit addresses.
  2. Screen Transaction checks both sides. Next to the flagged parties you get exposedAddresses, each with its role and highest exposure share.
  3. Low risk: credit it. Medium: send it to review with the exposure breakdown attached. High or sanctioned: hold it, pull the paths and follow your policy.

You set the thresholds. We give you the facts before money moves on your side.

What to watch for

  • Exposure is per chain. The same EVM address can be exposed on Ethereum and clean on BNB Smart Chain. Always pass the chain the deposit actually arrived on.
  • Read amounts from the proportional fields. Under the poison model every transfer after contact counts in full, so taintedReceived can be bigger than what really came in from the flagged source. proportionalReceived shows the flagged value itself.
  • Only received funds count. For direct contact, direction says whether the address received, sent or both. Sending to a flagged wallet is a different signal, and you'll want a different rule for it.
  • A zero score isn't proof of clean. Check isKnown in the Verify Address response. When it's false, we simply don't have a record of that address yet.

FAQ

What is crypto wallet exposure?

Wallet exposure is the share of funds an address received that can be traced back to a flagged source, such as a sanctioned entity or an exploiter, either directly or through intermediate addresses.

How many hops does Crypto APIs trace?

Up to 3 hops from sanctioned addresses and up to 2 from exploit addresses. Every result states the hop count, so you can tell a direct receipt from a two-hop one at a glance.

Which blockchains support exposure tracing?

Exposure runs on Bitcoin, Ethereum, BNB Smart Chain, Polygon, Tron, Solana, XRP, Litecoin and more. The Get Address Exposure docs list every supported chain.

Do I need a separate product for screening and exposure?

No. Address screening, transaction screening (KYT) and exposure are all part of the Crypto APIs AML API, documented on one public developer portal.

Start tracing

Exposure turns "the sender isn't on a list" into "here's where the money came from, hop by hop". See the AML API for what each check returns, then open the exposure endpoints on our developer portal and run your first query.

Share X f in

Build it on Crypto APIs

14-day free trial, mainnet included. No card needed.