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

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

Recovery pathway, how this casefile moves toward filing:

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

What we read in a WL casefile:

• Chains the WL 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 WL, the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
• Filings the WL 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:

• Hard line on WL, no seed-phrase requests, period.
• Hard line on WL, no remote logins requested.
• Hard line on WL, no upfront cash retainer.
• Hard line on WL, no guarantee language.
• Hard line on WL, no unsolicited phone outreach.