From the marginalia, the deposit pathway:

• Claimant deposit hashes, provided in the case submission and verified against the public ledger for FXFellow.
• Forwarding wallets on the deposit chain, each hop documented with the forwarding tx hash and the consolidating wallet.
• Bridge events into chains where the operator can off-ramp at scale.
• Mixer or privacy-service interactions, where present, listed with the contract address and the deposit/withdraw side.
• Off-ramp endpoint, the centralised exchange deposit address holding the compliance lever.

Off-ramp reading, exchange counterparty for FXFellow:

• FXFellow casefiles end at a centralised exchange, Bybit, KuCoin, OKX, or Gate.io are common; the casefile names the actual deposit address that received the consolidated funds.
• Off-ramp wallet for FXFellow is matched against compliance and chain-analytics datasets the Professor reads daily.
• Compliance leverage applied to the named off-ramp for FXFellow, the packet is delivered in compliance-desk format.
• Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the FXFellow casefile.

How a FXFellow casefile becomes a evidence filing:

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

Chains and off-ramps the Professor follows:

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