The annotation continues, off-ramp endpoint:

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

How a Portaltradecapital casefile becomes a evidence filing:

1. Triage on Portaltradecapital, submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
2. Trace on Portaltradecapital, deposit pathway mapped across chains, captured with chain of custody hashes.
3. Identify on Portaltradecapital, off-ramp endpoint matched to a named exchange counterparty.
4. File the Portaltradecapital packet, IC3, state AG (where loss meets state thresholds), off-ramp compliance desk, and civil-discovery overlay where dollar value supports it.
5. Follow-through on Portaltradecapital, the Professor stays on the casefile until a documented next step exists.

Reading-list, chains and exchanges in scope:

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