On-chain reading, wallet flow for FX Citizen:

• Claimant-to-platform deposit transactions on the deposit chain used by FX Citizen.
• 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 reading, exchange counterparty for FX Citizen:

• FX Citizen off-ramps consistently to centralised exchanges, Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The FX Citizen off-ramp address is matched to known compliance feeds, the Professor’s standing dataset plus chain-analytics references.
• Compliance leverage is applied at the named counterparty for FX Citizen, the packet meets the off-ramp’s published compliance standard.
• When the FX Citizen off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

Recovery pathway, how this casefile moves toward filing:

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

Recovery scammers do these things; the Professor never does:

• FX Citizen policy, seed phrases are never requested.
• FX Citizen policy, remote-access logins are never requested.
• FX Citizen policy, no upfront cash retainer to scope.
• FX Citizen policy, no guaranteed-recovery language. None.
• FX Citizen policy, no unsolicited calls. The Professor responds in writing only.