The annotation continues, off-ramp endpoint:

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

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

What the casefile records, chains and counterparties:

• Chains the Professor reads for xDelta casefiles, BTC, ETH, Tron USDT, BNB Smart Chain, Avalanche, Polygon, Arbitrum, Optimism, plus the cross-chain bridges that link them.
• Off-ramps named in xDelta, major centralised venues with compliance desks that accept regulator-grade packets.
• Filing pathways available on xDelta, IC3 for US claimants, state AG offices, off-ramp compliance, and civil-discovery overlay for high-value loss.