The Professor’s off-ramp note:

• Off-ramp endpoint for EFSPFX resolves to a named centralised counterparty, the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
• EFSPFX’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
• The compliance packet for EFSPFX is structured the way an off-ramp compliance reviewer expects to receive evidence, header, hashes, narrative, ask.
• If the EFSPFX off-ramp counterparty does not respond inside the published window, escalation routes through IC3, state AG, and civil discovery.

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

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

What we read in a EFSPFX casefile:

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

What the Professor will never do, by policy:

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