Off-ramp summary, Trade FDC casefile:

• Trade FDC casefiles end at a centralised exchange, Bybit, KuCoin, OKX, or Gate.io are common; the casefile names the actual deposit address that received the consolidated funds.
• Off-ramp wallet for Trade FDC is matched against compliance and chain-analytics datasets the Professor reads daily.
• Compliance leverage applied to the named off-ramp for Trade FDC, the packet is delivered in compliance-desk format.
• Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the Trade FDC casefile.

The Professor’s recovery note for Trade FDC:

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

What the casefile records, chains and counterparties:

• Chains tracked on Trade FDC, Bitcoin and Ethereum at the deposit side; Tron USDT-TRC20 and BSC at the consolidation side; bridges crossed where the operator chases liquidity.
• Off-ramps tracked on Trade FDC, named exchange counterparties with public compliance contacts.
• Filings supported on Trade FDC, IC3, state AG, off-ramp compliance, civil discovery, selected by the dollar value and the off-ramp’s responsiveness.

Lines the Professor will not cross:

• On the Trade FDC casefile, never request a seed phrase. Ever.
• On the Trade FDC casefile, never request remote-access logins to a wallet or exchange.
• On the Trade FDC casefile, never demand an upfront cash retainer to scope the matter.
• On the Trade FDC casefile, never promise a guaranteed recovery. The trail does not promise one.
• On the Trade FDC casefile, never call the claimant unsolicited. Written-only.