Off-ramp reading, exchange counterparty for SwizzPRO:

• SwizzPRO’s off-ramp endpoint, in this casefile, is the centralised exchange that holds compliance leverage, typically named in the packet alongside the deposit address.
• Chain-analytics datasets cross-reference the SwizzPRO off-ramp wallet against historical laundering throughput.
• The SwizzPRO packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
• Escalation pathways for SwizzPRO, where needed: IC3, the relevant state AG, and a civil-discovery overlay for KYC on the off-ramp wallet.

Recovery pathway, how this casefile moves toward filing:

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

What the casefile records, chains and counterparties:

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

What the Professor will never do, by policy:

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