Wallet trace — what the Professor maps:

• Deposit transaction hashes from the claimant wallet to the ChartLogic 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 reading — exchange counterparty for ChartLogic:

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

The Professor’s recovery note for ChartLogic:

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

Chains and off-ramps the Professor follows:

• Chains tracked on ChartLogic — Bitcoin and Ethereum at the deposit side; Tron USDT-TRC20 and BSC at the consolidation side; bridges crossed where the operator chases liquidity.
• Off-ramps tracked on ChartLogic — named exchange counterparties with public compliance contacts.
• Filings supported on ChartLogic — IC3, state AG, off-ramp compliance, civil discovery — selected by the dollar value and the off-ramp’s responsiveness.

What the Professor will never do — by policy:

• What the Professor will not do on ChartLogic — ask for a seed phrase.
• What the Professor will not do on ChartLogic — request remote-access logins.
• What the Professor will not do on ChartLogic — demand cash up front.
• What the Professor will not do on ChartLogic — promise a guarantee.
• What the Professor will not do on ChartLogic — call you out of the blue.