Trace summary — funds that left cfd-trader.io:

• Claimant-to-platform deposit transactions on the deposit chain used by CFD Trader.
• Operator-controlled forwarding wallets where deposits consolidate ahead of laundering or off-ramping.
• Cross-chain bridge events to chains with deeper exchange liquidity.
• Privacy-service interactions, where present in the trail.
• Off-ramp wallet — the named centralised-exchange endpoint.

From the lectern — off-ramp identification:

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

How a CFD Trader casefile becomes a regulator-ready filing:

1. Triage on CFD Trader — submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
2. Trace on CFD Trader — deposit pathway mapped across chains, captured with chain-of-custody hashes.
3. Identify on CFD Trader — off-ramp endpoint matched to a named exchange counterparty.
4. File the CFD Trader 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 CFD Trader — the Professor stays on the casefile until a documented next step exists.

What the Professor tracks across CFD Trader casefiles:

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

What is never asked of a claimant:

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