The annotation reads, wallet trace:

• Deposit transaction hashes from the claimant wallet to the XTB Global 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.

Off-ramp map, where the funds left the chain:

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

The Professor’s recovery note for XTB Global:

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