Wallet trace, what the Professor maps:

• Claimant deposit hashes, provided in the case submission and verified against the public ledger for Data FX.
• 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 reading, exchange counterparty for Data FX:

• Endpoint counterparty in the Data FX casefile is named, typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• Data FX’s off-ramp wallet is then matched against compliance feeds the Professor maintains a standing read on.
• Leverage is applied to that named counterparty, the Data FX packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the Data FX off-ramp is non-cooperative, the casefile escalates to IC3, the relevant state AG, and (where dollar value warrants) a civil-discovery overlay for KYC.

The Professor’s recovery note for Data FX:

1. Casefile review on Data FX, reading the submission against the no-go list.
2. Trace mapping on Data FX, pathway documented to chain of custody standard.
3. Off-ramp naming on Data FX, exchange endpoint identified.
4. Packet filing on Data FX, to the named off-ramp, IC3, state AG; civil discovery overlay as applicable.
5. Documented follow-through on Data FX.

What we read in a Data FX casefile:

• Chains tracked on Data FX, Bitcoin and Ethereum at the deposit side; Tron USDT-TRC20 and BSC at the consolidation side; bridges crossed where the operator chases liquidity.
• Off-ramps tracked on Data FX, named exchange counterparties with public compliance contacts.
• Filings supported on Data FX, IC3, state AG, off-ramp compliance, civil discovery, selected by the dollar value and the off-ramp’s responsiveness.

Boundaries on every Data FX casefile, never crossed:

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