From the marginalia, the deposit pathway:

• Deposit confirmations from the claimant to FX Trade’s receiving wallet at fxtradeterminal.com.
• Forwarding-wallet pathway documented hop-by-hop with chain of custody hashes.
• Cross-chain bridge transactions where the operator routed value out of the deposit chain.
• Mixer or coin-join interactions, where applicable.
• Final off-ramp at a centralised exchange, the compliance counterparty named in the recovery filing.

The annotation continues, off-ramp endpoint:

• Endpoint counterparty in the FX Trade casefile is named, typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• FX Trade’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 FX Trade packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the FX Trade 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.

Recovery pathway, how this casefile moves toward filing:

1. Read the FX Trade submission, written go/no-go returned.
2. Map the FX Trade wallet trail, every hop captured with chain of custody hashes.
3. Name the FX Trade off-ramp, endpoint counterparty identified.
4. Build and file the FX Trade recovery packet, to IC3, state AG, off-ramp compliance, civil-discovery overlay.
5. Stay on the FX Trade file, until written next steps exist.

What the casefile records, chains and counterparties:

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