The annotation reads — wallet trace:

• Deposit-side hashes from claimant wallets into TradeMasterCFD’s receiving addresses.
• Operator forwarding wallets — deposit consolidation documented to chain-of-custody standards.
• Inter-chain bridge transactions when value moves toward off-ramp liquidity.
• Mixer/obfuscation events the operator routed through, where present.
• Final off-ramp endpoint and named counterparty exchange.

The annotation continues — off-ramp endpoint:

• Off-ramp endpoint for TradeMasterCFD resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
• TradeMasterCFD’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
• The compliance packet for TradeMasterCFD is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
• If the TradeMasterCFD 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. Submission triage — TradeMasterCFD casefile reviewed against the no-go list, written reply within one business day.
2. Pathway trace — TradeMasterCFD deposit and forwarding wallets captured.
3. Endpoint identification — TradeMasterCFD off-ramp wallet named.
4. Filing — TradeMasterCFD packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
5. Ongoing follow — TradeMasterCFD stays on file until a documented next step is reached.

What the Professor tracks across TradeMasterCFD casefiles:

• Chains the TradeMasterCFD 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 TradeMasterCFD — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
• Filings the TradeMasterCFD packet supports — IC3, the appropriate state attorney general, the off-ramp’s compliance desk, and a civil-discovery overlay where dollar value justifies it.

Lines the Professor will not cross:

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