The annotation continues, off-ramp endpoint:

• On the Alphaprotrades casefile, the off-ramp endpoint resolves to a centralised exchange, Bitfinex, MEXC, or Crypto.com seen often in this segment, with the larger venues routed through under stress.
• The off-ramp wallet for Alphaprotrades is run against chain-analytics datasets and the Professor’s own compliance feeds.
• A evidence packet is delivered to the named counterparty, the Alphaprotrades casefile is built to the off-ramp’s compliance standard.
• Where the off-ramp will not engage, Alphaprotrades escalates to IC3, state AG, and civil-discovery overlay.

Recovery sequence, from on-chain reading to filed packet:

1. Submission triage, Alphaprotrades casefile reviewed against the no-go list, written reply within one business day.
2. Pathway trace, Alphaprotrades deposit and forwarding wallets captured.
3. Endpoint identification, Alphaprotrades off-ramp wallet named.
4. Filing, Alphaprotrades packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
5. Ongoing follow, Alphaprotrades stays on file until a documented next step is reached.

Reading-list, chains and exchanges in scope:

• Chains in scope for Alphaprotrades, the chains that handle the volume of casefile activity in this segment (BTC, ETH, Tron, BSC, plus L2s).
• Off-ramps in scope for Alphaprotrades, named centralised exchanges with compliance leverage.
• Filings supported on Alphaprotrades, IC3, state AG, off-ramp desk, civil discovery as applicable.

Boundaries on every Alphaprotrades casefile, never crossed:

• What the Professor will not do on Alphaprotrades, ask for a seed phrase.
• What the Professor will not do on Alphaprotrades, request remote-access logins.
• What the Professor will not do on Alphaprotrades, demand cash up front.
• What the Professor will not do on Alphaprotrades, promise a guarantee.
• What the Professor will not do on Alphaprotrades, call you out of the blue.