On-chain reading, wallet flow for GlobelFX:

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

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

Recovery sequence, from on-chain reading to filed packet:

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

Boundaries on every GlobelFX casefile, never crossed:

• On the GlobelFX casefile, never request a seed phrase. Ever.
• On the GlobelFX casefile, never request remote-access logins to a wallet or exchange.
• On the GlobelFX casefile, never demand an upfront cash retainer to scope the matter.
• On the GlobelFX casefile, never promise a guaranteed recovery. The trail does not promise one.
• On the GlobelFX casefile, never call the claimant unsolicited. Written-only.