The annotation reads, wallet trace:

• Deposit transaction hashes from the claimant wallet to the TradeZoom 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 summary, TradeZoom casefile:

• TradeZoom off-ramps consistently to centralised exchanges, Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The TradeZoom 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 TradeZoom, the packet meets the off-ramp’s published compliance standard.
• When the TradeZoom 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. Triage on TradeZoom, submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
2. Trace on TradeZoom, deposit pathway mapped across chains, captured with chain of custody hashes.
3. Identify on TradeZoom, off-ramp endpoint matched to a named exchange counterparty.
4. File the TradeZoom 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 TradeZoom, the Professor stays on the casefile until a documented next step exists.