Off-ramp map, where the funds left the chain:

• On the F1FX 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 F1FX is run against chain-analytics datasets and the Professor’s own compliance feeds.
• A evidence packet is delivered to the named counterparty, the F1FX casefile is built to the off-ramp’s compliance standard.
• Where the off-ramp will not engage, F1FX escalates to IC3, state AG, and civil-discovery overlay.

How a F1FX casefile becomes a evidence filing:

1. Casefile triage on F1FX, the submission is read; a written assessment is delivered.
2. Forensic trace on F1FX, every hop in the deposit pathway is captured and hashed.
3. Off-ramp identification, the F1FX endpoint is named.
4. Recovery filing on F1FX, packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
5. Continuing review of F1FX, the Professor follows the casefile until next-step documentation exists.

Reading-list, chains and exchanges in scope:

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

What the Professor will never do, by policy:

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