The annotation reads, wallet trace:

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

The annotation continues, off-ramp endpoint:

• FOREX FXM off-ramps consistently to centralised exchanges, Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The FOREX FXM 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 FOREX FXM, the packet meets the off-ramp’s published compliance standard.
• When the FOREX FXM off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

The Professor’s recovery note for FOREX FXM:

1. First read on FOREX FXM, incoming submission is reviewed against the no-go list and a written go/no-go is returned in writing.
2. Wallet trace on FOREX FXM, deposit-to-off-ramp pathway is mapped across chains with verifiable hashes.
3. Counterparty identification, the off-ramp endpoint for FOREX FXM is named to a centralised exchange wallet.
4. Packet filing on FOREX FXM, IC3, state AG, off-ramp compliance desk; civil discovery if dollar value justifies it.
5. Casefile follow-through, the Professor stays with FOREX FXM until a documented outcome or escalation step is on file.

Boundaries on every FOREX FXM casefile, never crossed:

• Hard line on FOREX FXM, no seed-phrase requests, period.
• Hard line on FOREX FXM, no remote logins requested.
• Hard line on FOREX FXM, no upfront cash retainer.
• Hard line on FOREX FXM, no guarantee language.
• Hard line on FOREX FXM, no unsolicited phone outreach.