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

• Coins.ph’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 Coins.ph off-ramp wallet against historical laundering throughput.
• The Coins.ph packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
• Escalation pathways for Coins.ph, 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 review on Coins.ph, reading the submission against the no-go list.
2. Trace mapping on Coins.ph, pathway documented to chain of custody standard.
3. Off-ramp naming on Coins.ph, exchange endpoint identified.
4. Packet filing on Coins.ph, to the named off-ramp, IC3, state AG; civil discovery overlay as applicable.
5. Documented follow-through on Coins.ph.

Reading-list, chains and exchanges in scope:

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

Boundaries on every Coins.ph casefile, never crossed:

• Hard line on Coins.ph, no seed-phrase requests, period.
• Hard line on Coins.ph, no remote logins requested.
• Hard line on Coins.ph, no upfront cash retainer.
• Hard line on Coins.ph, no guarantee language.
• Hard line on Coins.ph, no unsolicited phone outreach.