The annotation continues, off-ramp endpoint:

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

The Professor’s recovery note for Ocean8FX:

1. First read on Ocean8FX, incoming submission is reviewed against the no-go list and a written go/no-go is returned in writing.
2. Wallet trace on Ocean8FX, deposit-to-off-ramp pathway is mapped across chains with verifiable hashes.
3. Counterparty identification, the off-ramp endpoint for Ocean8FX is named to a centralised exchange wallet.
4. Packet filing on Ocean8FX, IC3, state AG, off-ramp compliance desk; civil discovery if dollar value justifies it.
5. Casefile follow-through, the Professor stays with Ocean8FX until a documented outcome or escalation step is on file.

Reading-list, chains and exchanges in scope:

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