On-chain reading — wallet flow for CEX.IO:

• Deposit-side hashes from claimant wallets into CEX.IO’s receiving addresses.
• Operator forwarding wallets — deposit consolidation documented to chain-of-custody standards.
• Inter-chain bridge transactions when value moves toward off-ramp liquidity.
• Mixer/obfuscation events the operator routed through, where present.
• Final off-ramp endpoint and named counterparty exchange.

Off-ramp summary — CEX.IO casefile:

• CEX.IO off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The CEX.IO 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 CEX.IO — the packet meets the off-ramp’s published compliance standard.
• When the CEX.IO off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

How a CEX.IO casefile becomes a regulator-ready filing:

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

What the casefile records — chains and counterparties:

• Chains in scope for CEX.IO — the chains that handle the volume of casefile activity in this segment (BTC, ETH, Tron, BSC, plus L2s).
• Off-ramps in scope for CEX.IO — named centralised exchanges with compliance leverage.
• Filings supported on CEX.IO — IC3, state AG, off-ramp desk, civil discovery as applicable.

Boundaries on every CEX.IO casefile — never crossed:

• CEX.IO policy — seed phrases are never requested.
• CEX.IO policy — remote-access logins are never requested.
• CEX.IO policy — no upfront cash retainer to scope.
• CEX.IO policy — no guaranteed-recovery language. None.
• CEX.IO policy — no unsolicited calls. The Professor responds in writing only.