The annotation continues, off-ramp endpoint:

• Endpoint counterparty in the CryptoFX 24 casefile is named, typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• CryptoFX 24’s off-ramp wallet is then matched against compliance feeds the Professor maintains a standing read on.
• Leverage is applied to that named counterparty, the CryptoFX 24 packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the CryptoFX 24 off-ramp is non-cooperative, the casefile escalates to IC3, the relevant state AG, and (where dollar value warrants) a civil-discovery overlay for KYC.

Recovery pathway, how this casefile moves toward filing:

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

Reading-list, chains and exchanges in scope:

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