Off-ramp summary, TCG casefile:

• Endpoint counterparty in the TCG casefile is named, typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• TCG’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 TCG packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the TCG 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 TCG submission, written go/no-go returned.
2. Map the TCG wallet trail, every hop captured with chain of custody hashes.
3. Name the TCG off-ramp, endpoint counterparty identified.
4. Build and file the TCG recovery packet, to IC3, state AG, off-ramp compliance, civil-discovery overlay.
5. Stay on the TCG file, until written next steps exist.

What the casefile records, chains and counterparties:

• Deposit + forwarding chains for TCG, Bitcoin, Ethereum, Tron USDT-TRC20, plus the smart-contract chains (BSC, Polygon, Avalanche, Arbitrum, Optimism) that cross via bridges.
• Off-ramps the TCG casefile may resolve to, centralised exchanges that respond to compliance filings.
• Filing pathways on TCG, IC3, state AG, off-ramp compliance, and civil-discovery overlay.