Here’s a quick, plain‑English heads‑up about how crypto flows are increasingly gated by risk scores—and why that matters for traders, founders, and anyone moving coins.
What’s happening
Exchanges, custodians, and wallets now run address/entity risk scoring on deposits/withdrawals. Tools like Chainalysis KYT/Address Screening and TRM Transaction Monitoring/Entity Risk flag or block flows in real time.
Scoring blends on‑chain heuristics/attribution with policy rules (sanctions exposure, hacks/ransomware links, mixers, darknet ties, etc.). Scores are typically Low/Medium/High/Severe and trigger alerts, holds, or re‑KYC.
Big venues publicly discuss ML‑based address risk scoring at scale (e.g., Coinbase’s system to predict risky counterparties beyond their platform).
This is largely driven by sanctions/AML expectations: OFAC’s guidance tells the industry to screen addresses, IP/geolocation, and keep risk‑based programs—no new law needed for a venue to freeze/deny a transfer.
How it affects you
Deposits can be delayed or blocked if your coins have indirect exposure (e.g., multiple hops from a sanctioned/hacked pool). Even “clean” users can get flagged via counterparty exposure.
Off‑exchange wallets are not immune: many providers embed screening and continuous rescoring.
Appeals = documentation: expect to provide source‑of‑funds/transaction trails; the venue’s score often keys off the highest‑risk indicator in the graph.
Practical moves (fast list)
Keep a clean routing wallet: receive funds there first, then forward to exchanges; don’t co‑mix high‑risk counterparties. (Reduces inherited exposure risk.)
Label & export proofs (tx notes, invoices, mining/payout records) so you can answer compliance reviews quickly. (Aligned with risk‑based programs venues follow.)
Before sending to an exchange, pre‑screen counterparties using a third‑party checker or the venue’s own KYT APIs where available.
Avoid bridging/mixing paths tied to sanctioned or hacked flows; even indirect contact can push a score into “review/block.”