Reading the wallets, OTC 500 casefile:

• Claimant-to-platform deposit transactions on the deposit chain used by OTC 500.
• Operator-controlled forwarding wallets where deposits consolidate ahead of laundering or off-ramping.
• Cross-chain bridge events to chains with deeper exchange liquidity.
• Privacy-service interactions, where present in the trail.
• Off-ramp wallet, the named centralised-exchange endpoint.

The annotation continues, off-ramp endpoint:

• On the OTC 500 casefile, the off-ramp endpoint resolves to a centralised exchange, Bitfinex, MEXC, or Crypto.com seen often in this segment, with the larger venues routed through under stress.
• The off-ramp wallet for OTC 500 is run against chain-analytics datasets and the Professor’s own compliance feeds.
• A evidence packet is delivered to the named counterparty, the OTC 500 casefile is built to the off-ramp’s compliance standard.
• Where the off-ramp will not engage, OTC 500 escalates to IC3, state AG, and civil-discovery overlay.

Recovery pathway, how this casefile moves toward filing:

1. Submission triage, OTC 500 casefile reviewed against the no-go list, written reply within one business day.
2. Pathway trace, OTC 500 deposit and forwarding wallets captured.
3. Endpoint identification, OTC 500 off-ramp wallet named.
4. Filing, OTC 500 packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
5. Ongoing follow, OTC 500 stays on file until a documented next step is reached.

Reading-list, chains and exchanges in scope:

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