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

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

How a YazhiFX casefile becomes a evidence filing:

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

What the casefile records, chains and counterparties:

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

Boundaries on every YazhiFX casefile, never crossed:

• On the YazhiFX casefile, never request a seed phrase. Ever.
• On the YazhiFX casefile, never request remote-access logins to a wallet or exchange.
• On the YazhiFX casefile, never demand an upfront cash retainer to scope the matter.
• On the YazhiFX casefile, never promise a guaranteed recovery. The trail does not promise one.
• On the YazhiFX casefile, never call the claimant unsolicited. Written-only.