The annotation continues, off-ramp endpoint:

• Coinvx off-ramps consistently to centralised exchanges, Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The Coinvx off-ramp address is matched to known compliance feeds, the Professor’s standing dataset plus chain-analytics references.
• Compliance leverage is applied at the named counterparty for Coinvx, the packet meets the off-ramp’s published compliance standard.
• When the Coinvx off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

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

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

Chains and off-ramps the Professor follows:

• Deposit-side chains in Coinvx casefiles, typically the major chains (BTC, ETH) and the high-throughput stablecoin chains (Tron USDT, BSC USDT), with bridge crossings noted.
• Off-ramps named in Coinvx packets, centralised exchanges that accept regulator-grade compliance filings.
• Filing options on Coinvx, IC3 (US), state AG, off-ramp compliance desk, civil-discovery KYC where the dollar value warrants it.

Boundaries on every Coinvx casefile, never crossed:

• Hard line on Coinvx, no seed-phrase requests, period.
• Hard line on Coinvx, no remote logins requested.
• Hard line on Coinvx, no upfront cash retainer.
• Hard line on Coinvx, no guarantee language.
• Hard line on Coinvx, no unsolicited phone outreach.