On-chain reading, wallet flow for CCOOK:

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

How a CCOOK casefile becomes a evidence filing:

1. Casefile triage on CCOOK, the submission is read; a written assessment is delivered.
2. Forensic trace on CCOOK, every hop in the deposit pathway is captured and hashed.
3. Off-ramp identification, the CCOOK endpoint is named.
4. Recovery filing on CCOOK, packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
5. Continuing review of CCOOK, the Professor follows the casefile until next-step documentation exists.

What the casefile records, chains and counterparties:

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