The annotation continues, off-ramp endpoint:

• Endpoint counterparty in the TenX Prime casefile is named, typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• TenX Prime’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 TenX Prime packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the TenX Prime 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.

The Professor’s recovery note for TenX Prime:

1. Casefile review on TenX Prime, reading the submission against the no-go list.
2. Trace mapping on TenX Prime, pathway documented to chain of custody standard.
3. Off-ramp naming on TenX Prime, exchange endpoint identified.
4. Packet filing on TenX Prime, to the named off-ramp, IC3, state AG; civil discovery overlay as applicable.
5. Documented follow-through on TenX Prime.

Reading-list, chains and exchanges in scope:

• Chains tracked on TenX Prime, Bitcoin and Ethereum at the deposit side; Tron USDT-TRC20 and BSC at the consolidation side; bridges crossed where the operator chases liquidity.
• Off-ramps tracked on TenX Prime, named exchange counterparties with public compliance contacts.
• Filings supported on TenX Prime, IC3, state AG, off-ramp compliance, civil discovery, selected by the dollar value and the off-ramp’s responsiveness.