Off-ramp reading, exchange counterparty for USP Capital:

• USP Capital’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 USP Capital off-ramp wallet against historical laundering throughput.
• The USP Capital packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
• Escalation pathways for USP Capital, where needed: IC3, the relevant state AG, and a civil-discovery overlay for KYC on the off-ramp wallet.

Recovery sequence, from on-chain reading to filed packet:

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

Reading-list, chains and exchanges in scope:

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

Boundaries on every USP Capital casefile, never crossed:

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