Off-ramp reading, exchange counterparty for PSFX:

• PSFX off-ramps consistently to centralised exchanges, Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The PSFX 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 PSFX, the packet meets the off-ramp’s published compliance standard.
• When the PSFX off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

Recovery pathway, how this casefile moves toward filing:

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

Chains and off-ramps the Professor follows:

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

What the Professor will never do, by policy:

• PSFX policy, seed phrases are never requested.
• PSFX policy, remote-access logins are never requested.
• PSFX policy, no upfront cash retainer to scope.
• PSFX policy, no guaranteed-recovery language. None.
• PSFX policy, no unsolicited calls. The Professor responds in writing only.