Off-ramp map, where the funds left the chain:

• UeTrades 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 UeTrades is matched against compliance and chain-analytics datasets the Professor reads daily.
• Compliance leverage applied to the named off-ramp for UeTrades, the packet is delivered in compliance-desk format.
• Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the UeTrades casefile.

Recovery pathway, how this casefile moves toward filing:

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

What we read in a UeTrades casefile:

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

Lines the Professor will not cross:

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