From the marginalia, the deposit pathway:

• Deposit transaction hashes from the claimant wallet to the HashXCapital platform receiving address.
• Forwarding wallets the platform consolidated through, typically two to four hops on the deposit chain (BTC / ETH / USDT-TRC20 / BSC / Polygon / Arbitrum / Optimism / Avalanche).
• Bridge crossings between chains, where the operator moves value into a chain with deeper liquidity ahead of the off-ramp.
• Mixer interactions, Tornado-Cash variants, Sinbad, and the smaller obfuscation services that operators rotate through under regulatory pressure.
• Final off-ramp wallet, the centralised exchange deposit address that received the consolidated funds.

The Professor’s off-ramp note:

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

The Professor’s recovery note for HashXCapital:

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