Reading the wallets, Tradize casefile:

• Claimant deposit hashes, provided in the case submission and verified against the public ledger for Tradize.
• 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 map, where the funds left the chain:

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

The Professor’s recovery note for Tradize:

1. First read on Tradize, incoming submission is reviewed against the no-go list and a written go/no-go is returned in writing.
2. Wallet trace on Tradize, deposit-to-off-ramp pathway is mapped across chains with verifiable hashes.
3. Counterparty identification, the off-ramp endpoint for Tradize is named to a centralised exchange wallet.
4. Packet filing on Tradize, IC3, state AG, off-ramp compliance desk; civil discovery if dollar value justifies it.
5. Casefile follow-through, the Professor stays with Tradize until a documented outcome or escalation step is on file.