Off-ramp summary, CMI Trader casefile:

• CMI Trader off-ramps consistently to centralised exchanges, Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The CMI Trader off-ramp address is matched to known compliance feeds, the Professor’s standing dataset plus chain-analytics references.
• Compliance leverage is applied at the named counterparty for CMI Trader, the packet meets the off-ramp’s published compliance standard.
• When the CMI Trader off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

Recovery pathway, how this casefile moves toward filing:

1. Read the CMI Trader submission, written go/no-go returned.
2. Map the CMI Trader wallet trail, every hop captured with chain of custody hashes.
3. Name the CMI Trader off-ramp, endpoint counterparty identified.
4. Build and file the CMI Trader recovery packet, to IC3, state AG, off-ramp compliance, civil-discovery overlay.
5. Stay on the CMI Trader file, until written next steps exist.

What we read in a CMI Trader casefile:

• Chains tracked on CMI Trader, 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 CMI Trader, named exchange counterparties with public compliance contacts.
• Filings supported on CMI Trader, 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:

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