Reading the wallets — CFD Merchants casefile:

• Deposit transaction hashes from the claimant wallet to the CFD Merchants platform receiving address.
• Forwarding wallets the platform consolidated through — typically two to four hops on the deposit chain (BTC / ETH / USDT-TRC20 / BSC / Polygon / Arbitrum / Optimism / Avalanche).
• Bridge crossings between chains, where the operator moves value into a chain with deeper liquidity ahead of the off-ramp.
• Mixer interactions — Tornado-Cash variants, Sinbad, and the smaller obfuscation services that operators rotate through under regulatory pressure.
• Final off-ramp wallet — the centralised exchange deposit address that received the consolidated funds.

Off-ramp reading — exchange counterparty for CFD Merchants:

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

Pathway to recovery — what happens after the trail is mapped:

1. Casefile review on CFD Merchants — reading the submission against the no-go list.
2. Trace mapping on CFD Merchants — pathway documented to chain-of-custody standard.
3. Off-ramp naming on CFD Merchants — exchange endpoint identified.
4. Packet filing on CFD Merchants — to the named off-ramp, IC3, state AG; civil discovery overlay as applicable.
5. Documented follow-through on CFD Merchants.

Reading-list — chains and exchanges in scope:

• Deposit + forwarding chains for CFD Merchants — Bitcoin, Ethereum, Tron USDT-TRC20, plus the smart-contract chains (BSC, Polygon, Avalanche, Arbitrum, Optimism) that cross via bridges.
• Off-ramps the CFD Merchants casefile may resolve to — centralised exchanges that respond to compliance filings.
• Filing pathways on CFD Merchants — IC3, state AG, off-ramp compliance, and civil-discovery overlay.

Lines the Professor will not cross:

• CFD Merchants policy — seed phrases are never requested.
• CFD Merchants policy — remote-access logins are never requested.
• CFD Merchants policy — no upfront cash retainer to scope.
• CFD Merchants policy — no guaranteed-recovery language. None.
• CFD Merchants policy — no unsolicited calls. The Professor responds in writing only.