The annotation continues, off-ramp endpoint:

• Endpoint counterparty in the CentralTradingHub casefile is named, typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• CentralTradingHub’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 CentralTradingHub packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the CentralTradingHub 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. Casefile triage on CentralTradingHub, the submission is read; a written assessment is delivered.
2. Forensic trace on CentralTradingHub, every hop in the deposit pathway is captured and hashed.
3. Off-ramp identification, the CentralTradingHub endpoint is named.
4. Recovery filing on CentralTradingHub, packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
5. Continuing review of CentralTradingHub, the Professor follows the casefile until next-step documentation exists.

What the casefile records, chains and counterparties:

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