The annotation reads — wallet trace:

• Deposit transaction hashes from the claimant wallet to the CFDHolding 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.

The annotation continues — off-ramp endpoint:

• Endpoint counterparty in the CFDHolding casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• CFDHolding’s off-ramp wallet is then matched against compliance feeds the Professor maintains a standing read on.
• Leverage is applied to that named counterparty — the CFDHolding packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the CFDHolding off-ramp is non-cooperative, the casefile escalates to IC3, the relevant state AG, and (where dollar value warrants) a civil-discovery overlay for KYC.

Recovery pathway — how this casefile moves toward filing:

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

What the casefile records — chains and counterparties:

• Chains the CFDHolding casefile may touch — Bitcoin and Ethereum at the deposit side, Tron USDT-TRC20 in stablecoin pathways, BNB Smart Chain and the L2s (Arbitrum, Optimism, Polygon, Base) where bridges link them.
• Off-ramps relevant to CFDHolding — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
• Filings the CFDHolding packet supports — IC3, the appropriate state attorney general, the off-ramp’s compliance desk, and a civil-discovery overlay where dollar value justifies it.

What is never asked of a claimant:

• Boundary on CFDHolding — seed phrases are off-limits.
• Boundary on CFDHolding — remote logins are off-limits.
• Boundary on CFDHolding — upfront cash retainers are off-limits.
• Boundary on CFDHolding — guaranteed-recovery promises are off-limits.
• Boundary on CFDHolding — unsolicited outbound contact is off-limits.