The annotation continues, off-ramp endpoint:

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

How a AlfaXM casefile becomes a evidence filing:

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

What we read in a AlfaXM casefile:

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