v1 → v2
Scores
trust_score0 → 0
severity_base— → —
score_modifier0 → 0
Sections
Overview of Enforcement Action → Overview of the Enforcement Action
unchanged
Case 1: United States v. Approximately 1,766,583 USDT (No. 26-cv-2540) — MicMarkets FX Romance Fraud → Complaint 26-cv-2540: MicMarkets FX Romance Fraud (~1,766,583 USDT)
unchanged
Case 2: United States v. Approximately 2,389,778.77 USDT (No. 26-cv-2539) — Zoomex Exchange Spoofing → Complaint 26-cv-2539: Zoomex Exchange Spoofing (~2,389,778.77 USDT)
unchanged
Case 3: United States v. Approximately 10,404,905 USDT (No. 26-cv-2542) — Multi-Platform Investment Fraud Network → Complaint 26-cv-2542: Multi-Platform Investment Fraud Network (~10,404,905 USDT)
unchanged
Case 4: United States v. Approximately 284,903.78 USDT (No. 26-cv-2541) — Two-Stage Recovery Fraud → Complaint 26-cv-2541: Two-Stage Recovery Fraud (~284,903.78 USDT)
unchanged
Case 5: United States v. Approximately 1,230,899.74 USDT (No. 26-cv-2543) — National Capital Region Victim → Complaint 26-cv-2543: National Capital Region Victim (~1,230,899.74 USDT)
unchanged
Fraud Typology: Pig Butchering and Derivative Schemes → Fraud Typology and Victim Impact
unchanged
Geographic Scope and Alleged Operator Networks → Laundering Methods and On-Chain Tracing
unchanged
Scam Center Strike Force Background → Geographic Scope and Alleged Operator Networks
unchanged
Cryptocurrency and Blockchain Technical Details → D.C. Scam Center Strike Force
unchanged
Legal Framework and Procedural Notes → Legal Framework and Victim Recovery Path
unchanged
Timeline events
+ added2025 — (no description)
+ added2025-07 — (no description)
+ added2026-05 — (no description)
+ added2026-07 — (no description)
- removed2026-05-27 — (no description)
- removed2026-07-21 — (no description)
- removed2026-07-22 — (no description)
~ changed2023: “” → “”
~ changed2024-11: “” → “”
~ changed2025-11: “” → “”
~ changed2026: “” → “”
~ changed2026-02: “” → “”
~ changed2026-04: “” → “”
Accepted submissions
No changes to accepted submissions.
Each version is bound to the decision event that created it. Verify the chain anchor for either via the audit log.
v1 hash: 41379edc05e35f046e042ea4999e978ffe3a6d7790b11daf77d979ba00851072
v2 hash: 22566e437b79a00f32c332c17b64ce1ac1df83f56496b4e418a13cb743eb9b1f