On-chain reading — wallet flow for Tradercode:

• Claimant deposit hashes — provided in the case submission and verified against the public ledger for Tradercode.
• 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:

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

Recovery sequence — from on-chain reading to filed packet:

1. Triage on Tradercode — submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
2. Trace on Tradercode — deposit pathway mapped across chains, captured with chain-of-custody hashes.
3. Identify on Tradercode — off-ramp endpoint matched to a named exchange counterparty.
4. File the Tradercode 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 Tradercode — the Professor stays on the casefile until a documented next step exists.

Reading-list — chains and exchanges in scope:

• Chains the Tradercode 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 Tradercode — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
• Filings the Tradercode packet supports — IC3, the appropriate state attorney general, the off-ramp’s compliance desk, and a civil-discovery overlay where dollar value justifies it.

Lines we never cross — by published policy:

• Boundary on Tradercode — seed phrases are off-limits.
• Boundary on Tradercode — remote logins are off-limits.
• Boundary on Tradercode — upfront cash retainers are off-limits.
• Boundary on Tradercode — guaranteed-recovery promises are off-limits.
• Boundary on Tradercode — unsolicited outbound contact is off-limits.