Off-ramp summary, Expert Trade casefile:

• Endpoint counterparty in the Expert Trade casefile is named, typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• Expert Trade’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 Expert Trade packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the Expert Trade 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.

How a Expert Trade casefile becomes a evidence filing:

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

Chains and off-ramps the Professor follows:

• Chains in scope for Expert Trade, the chains that handle the volume of casefile activity in this segment (BTC, ETH, Tron, BSC, plus L2s).
• Off-ramps in scope for Expert Trade, named centralised exchanges with compliance leverage.
• Filings supported on Expert Trade, IC3, state AG, off-ramp desk, civil discovery as applicable.

Lines the Professor will not cross:

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