01
USDT freeze fact
Built from TronScan’s stablecoin blacklist index and a direct Tether USDT contract read. Agreement yields blacklisted or no_direct_match; disagreement or partial success is inconclusive.
Methodology
What the TRON USDT risk score checks
The platform separates independent freeze and OFAC facts from a deterministic risk-indicator score built from public data. Every result is meant to support human review, not automate a compliance decision.
Scoring version: 2026-07-29.v2
Risk scores are informational indicators only. They are not legal advice, a compliance determination, or an automated accept/reject instruction.
Upstream source roles and freshness behavior are documented on the data sources page.
Independent facts vs risk indicators
02
OFAC fact
Exact normalized match against the locally cached OFAC TRON dataset. Status is exact_match, no_exact_match, or unavailable when the dataset cannot be used.
03
Risk indicators
A 0–100 score with tier, evidence confidence, and a breakdown of named signals. Hard signals dominate; derived signals add only when public coverage supports them.
Hard signals
Hard signals dominate the risk-indicator score without rewriting the independent freeze or OFAC facts. The score starts at 0; there is no baseline risk contribution.
OFAC exact match
Exact match in the locally cached OFAC TRON dataset sets the risk-indicator score to 100 and tier severe. The independent OFAC fact is reported separately from freeze status.
OpenSanctions legal sanctions
A legal-sanctions wallet match also scores 100 / severe and does not stack with OFAC.
Direct USDT blacklist agreement
When TronScan and the live Tether contract agree that an address is blacklisted, freeze status is blacklisted and the risk-indicator score is 100 / severe.
Inconclusive freeze signal
A fresh active Tether-history signal or one positive direct blacklist source without agreement scores 95 / severe while the primary freeze status remains inconclusive.
Derived signals
Derived contributions are bounded by observed public-source coverage. Removed Tether events and destroyed-funds history remain evidence-only. Raw volume, transaction count, activity windows, and entity tags are context-only and contribute zero points. Every nonzero score item must include at least one visible finding ID and structured evidence.
| Signal | Contribution |
|---|---|
| OpenSanctions crime-intelligence match | +35 once |
| Chainabuse moderator-verified report(s) | +30 once |
| 1-hop inbound exposure to sanctioned counterparties | +20, or +30 when flagged volume share ≥ 10% |
| 1-hop inbound exposure to USDT-blacklisted counterparties | +25 |
| Sampled 2-hop proximity to flagged sources | +10 |
| Fast-in / fast-out heuristic | +15 |
| Peel-chain-like outflow burst | +10 |
| Structuring-like inbound deposits | +8 |
| High inbound concentration (complete window, ≥20 inbound transfers, top share ≥ 80%) | +8 |
Risk tiers
Low
0–19
Guarded
20–39
Elevated
40–69
High
70–89
Severe
90–100
Tier thresholds: guarded at 20, elevated at 40, high at 70, severe at 90.
Evidence confidence
Confidence describes the credibility of evidence used by a fact or scored indicator. It is separate from the risk score: a high score can still have reduced confidence when sources are partial or truncated.
- Freeze confidence is 100 when the live contract read succeeds, 90 when only TronScan succeeds, and 0 otherwise.
- OFAC confidence is 100 for fresh data, 92 for aging data, 85 for an exact match in stale data, and 0 when unavailable. Stale negative screens are unavailable.
- Risk confidence is the minimum confidence of nonzero evidence items. A zero score uses the minimum confidence of completed negative checks.
- Transfer pagination caps affected evidence at 92; designed 2-hop sampling caps it at 92, or 84 when combined with truncated transfer history.
- Locked and failed checks do not reduce evidence confidence; they appear in coverage instead.
Coverage and bounded windows
Coverage reports completed, locked, failed, and sampled checks separately. Transfer-derived results include requested and observed windows, transfer counts, fetched pages, and truncation state. Two-hop tracing is always sampled. Transfer analysis uses a bounded public history window rather than full-chain reconstruction.
Anonymous reports run the two direct USDT methods, Tether event history, exact OFAC screening, and inexpensive balance context. Broader AML sources and transfer analysis are locked until sign-in.
Evidence policy
Freshness is part of the result
Sanctions and issuer controls can change without warning. Reports surface source freshness, unavailable checks, evidence confidence, and coverage so reviewers can see whether an assessment is complete enough for the decision at hand.
What the score does not do
It does not predict future Tether freezes.
It does not replace legal counsel or a regulated compliance program.
It does not ask for seed phrases, private keys, or wallet signatures.
Practical operator guides
Screening fundamentals
USDT Blacklist, OFAC Sanctions and AML Risk: What’s the Difference?
Separate Tether's issuer blacklist, exact OFAC address matches, and heuristic AML indicators when reviewing a TRON USDT counterparty.
Interpreting evidence
How to Read a TRON USDT Risk Report
Read freeze facts, sanctions results, risk score, confidence, source freshness, and incomplete coverage without mistaking missing evidence for safety.