The annotation continues, off-ramp endpoint:

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

Recovery sequence, from on-chain reading to filed packet:

1. First read on CryptFxTrade, incoming submission is reviewed against the no-go list and a written go/no-go is returned in writing.
2. Wallet trace on CryptFxTrade, deposit-to-off-ramp pathway is mapped across chains with verifiable hashes.
3. Counterparty identification, the off-ramp endpoint for CryptFxTrade is named to a centralised exchange wallet.
4. Packet filing on CryptFxTrade, IC3, state AG, off-ramp compliance desk; civil discovery if dollar value justifies it.
5. Casefile follow-through, the Professor stays with CryptFxTrade until a documented outcome or escalation step is on file.

Chains and off-ramps the Professor follows:

• Deposit-side chains in CryptFxTrade 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 CryptFxTrade packets, centralised exchanges that accept regulator-grade compliance filings.
• Filing options on CryptFxTrade, IC3 (US), state AG, off-ramp compliance desk, civil-discovery KYC where the dollar value warrants it.