Trace summary — funds that left fxhubs.com:

• Initial deposit hashes to the FX HUBS receiving address at fxhubs.com.
• Hop-by-hop forwarding wallets across the deposit chain, captured with chain-of-custody hashes.
• Cross-chain bridge events that move value into the chain where liquidity supports the eventual off-ramp.
• Obfuscation events through mixer contracts and privacy services.
• Centralised-exchange off-ramp wallets — the named counterparty that holds compliance leverage.

The annotation continues — off-ramp endpoint:

• Off-ramp endpoint for FX HUBS resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
• FX HUBS’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
• The compliance packet for FX HUBS is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
• If the FX HUBS off-ramp counterparty does not respond inside the published window, escalation routes through IC3, state AG, and civil discovery.

Filing pathway — the next step after the off-ramp is identified:

1. Triage on FX HUBS — submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
2. Trace on FX HUBS — deposit pathway mapped across chains, captured with chain-of-custody hashes.
3. Identify on FX HUBS — off-ramp endpoint matched to a named exchange counterparty.
4. File the FX HUBS packet — IC3, state AG (where loss meets state thresholds), off-ramp compliance desk, and civil-discovery overlay where dollar value supports it.
5. Follow-through on FX HUBS — the Professor stays on the casefile until a documented next step exists.

What the casefile records — chains and counterparties:

• Chains in scope for FX HUBS — the chains that handle the volume of casefile activity in this segment (BTC, ETH, Tron, BSC, plus L2s).
• Off-ramps in scope for FX HUBS — named centralised exchanges with compliance leverage.
• Filings supported on FX HUBS — IC3, state AG, off-ramp desk, civil discovery as applicable.

Boundaries on every FX HUBS casefile — never crossed:

• What the Professor will not do on FX HUBS — ask for a seed phrase.
• What the Professor will not do on FX HUBS — request remote-access logins.
• What the Professor will not do on FX HUBS — demand cash up front.
• What the Professor will not do on FX HUBS — promise a guarantee.
• What the Professor will not do on FX HUBS — call you out of the blue.