On-chain reading, wallet flow for ForexPixel:

• Claimant-to-platform deposit transactions on the deposit chain used by ForexPixel.
• 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 map, where the funds left the chain:

• ForexPixel 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 ForexPixel is matched against compliance and chain-analytics datasets the Professor reads daily.
• Compliance leverage applied to the named off-ramp for ForexPixel, the packet is delivered in compliance-desk format.
• Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the ForexPixel casefile.

How a ForexPixel casefile becomes a evidence filing:

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

Chains and off-ramps the Professor follows:

• Deposit-side chains in ForexPixel 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 ForexPixel packets, centralised exchanges that accept regulator-grade compliance filings.
• Filing options on ForexPixel, IC3 (US), state AG, off-ramp compliance desk, civil-discovery KYC where the dollar value warrants it.