From the marginalia, the deposit pathway:

• Claimant-to-platform deposit transactions on the deposit chain used by ByteFX.
• 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.

Off-ramp summary, ByteFX casefile:

• Endpoint counterparty in the ByteFX casefile is named, typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• ByteFX’s off-ramp wallet is then matched against compliance feeds the Professor maintains a standing read on.
• Leverage is applied to that named counterparty, the ByteFX packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the ByteFX off-ramp is non-cooperative, the casefile escalates to IC3, the relevant state AG, and (where dollar value warrants) a civil-discovery overlay for KYC.

How a ByteFX casefile becomes a evidence filing:

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

Reading-list, chains and exchanges in scope:

• Deposit-side chains in ByteFX casefiles, typically the major chains (BTC, ETH) and the high-throughput stablecoin chains (Tron USDT, BSC USDT), with bridge crossings noted.
• Off-ramps named in ByteFX packets, centralised exchanges that accept regulator-grade compliance filings.
• Filing options on ByteFX, IC3 (US), state AG, off-ramp compliance desk, civil-discovery KYC where the dollar value warrants it.