Off-ramp summary, NIYAFA FX casefile:

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

How a NIYAFA FX casefile becomes a evidence filing:

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

What the casefile records, chains and counterparties:

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

What the Professor will never do, by policy:

• Boundary on NIYAFA FX, seed phrases are off-limits.
• Boundary on NIYAFA FX, remote logins are off-limits.
• Boundary on NIYAFA FX, upfront cash retainers are off-limits.
• Boundary on NIYAFA FX, guaranteed-recovery promises are off-limits.
• Boundary on NIYAFA FX, unsolicited outbound contact is off-limits.