On-chain reading, wallet flow for TradeHUB:

• Deposit confirmations from the claimant to TradeHUB’s receiving wallet at tradehub.fm.
• Forwarding-wallet pathway documented hop-by-hop with chain of custody hashes.
• Cross-chain bridge transactions where the operator routed value out of the deposit chain.
• Mixer or coin-join interactions, where applicable.
• Final off-ramp at a centralised exchange, the compliance counterparty named in the recovery filing.

The Professor’s off-ramp note:

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

The Professor’s recovery note for TradeHUB:

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

Chains and off-ramps the Professor follows:

• Chains the TradeHUB casefile may touch, Bitcoin and Ethereum at the deposit side, Tron USDT-TRC20 in stablecoin pathways, BNB Smart Chain and the L2s (Arbitrum, Optimism, Polygon, Base) where bridges link them.
• Off-ramps relevant to TradeHUB, the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
• Filings the TradeHUB packet supports, IC3, the appropriate state attorney general, the off-ramp’s compliance desk, and a civil-discovery overlay where dollar value justifies it.