The annotation continues, off-ramp endpoint:

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

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

1. Casefile triage on FXQM, the submission is read; a written assessment is delivered.
2. Forensic trace on FXQM, every hop in the deposit pathway is captured and hashed.
3. Off-ramp identification, the FXQM endpoint is named.
4. Recovery filing on FXQM, packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
5. Continuing review of FXQM, the Professor follows the casefile until next-step documentation exists.

Chains and off-ramps the Professor follows:

• Chains the FXQM 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 FXQM, the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
• Filings the FXQM packet supports, IC3, the appropriate state attorney general, the off-ramp’s compliance desk, and a civil-discovery overlay where dollar value justifies it.

Boundaries on every FXQM casefile, never crossed:

• What the Professor will not do on FXQM, ask for a seed phrase.
• What the Professor will not do on FXQM, request remote-access logins.
• What the Professor will not do on FXQM, demand cash up front.
• What the Professor will not do on FXQM, promise a guarantee.
• What the Professor will not do on FXQM, call you out of the blue.