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

• HaveTrade off-ramps consistently to centralised exchanges, Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The HaveTrade 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 HaveTrade, the packet meets the off-ramp’s published compliance standard.
• When the HaveTrade off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

The Professor’s recovery note for HaveTrade:

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

What we read in a HaveTrade casefile:

• Deposit-side chains in HaveTrade casefiles, typically the major chains (BTC, ETH) and the high-throughput stablecoin chains (Tron USDT, BSC USDT), with bridge crossings noted.
• Off-ramps named in HaveTrade packets, centralised exchanges that accept regulator-grade compliance filings.
• Filing options on HaveTrade, IC3 (US), state AG, off-ramp compliance desk, civil-discovery KYC where the dollar value warrants it.

Recovery scammers do these things; the Professor never does:

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