Off-ramp reading, exchange counterparty for Phantom Light:

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

How a Phantom Light casefile becomes a evidence filing:

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

Reading-list, chains and exchanges in scope:

• Chains tracked on Phantom Light, Bitcoin and Ethereum at the deposit side; Tron USDT-TRC20 and BSC at the consolidation side; bridges crossed where the operator chases liquidity.
• Off-ramps tracked on Phantom Light, named exchange counterparties with public compliance contacts.
• Filings supported on Phantom Light, IC3, state AG, off-ramp compliance, civil discovery, selected by the dollar value and the off-ramp’s responsiveness.