The annotation continues, off-ramp endpoint:

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

How a SnapEx Fx casefile becomes a evidence filing:

1. Triage on SnapEx Fx, submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
2. Trace on SnapEx Fx, deposit pathway mapped across chains, captured with chain of custody hashes.
3. Identify on SnapEx Fx, off-ramp endpoint matched to a named exchange counterparty.
4. File the SnapEx Fx packet, IC3, state AG (where loss meets state thresholds), off-ramp compliance desk, and civil-discovery overlay where dollar value supports it.
5. Follow-through on SnapEx Fx, the Professor stays on the casefile until a documented next step exists.

What the casefile records, chains and counterparties:

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