Reading the wallets, FXGLT casefile:

• Claimant deposit hashes, provided in the case submission and verified against the public ledger for FXGLT.
• 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 summary, FXGLT casefile:

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

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

1. Triage on FXGLT, submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
2. Trace on FXGLT, deposit pathway mapped across chains, captured with chain of custody hashes.
3. Identify on FXGLT, off-ramp endpoint matched to a named exchange counterparty.
4. File the FXGLT packet, IC3, state AG (where loss meets state thresholds), off-ramp compliance desk, and civil-discovery overlay where dollar value supports it.
5. Follow-through on FXGLT, the Professor stays on the casefile until a documented next step exists.