On-chain reading — wallet flow for Clone ZBX:

• Deposit confirmations from the claimant to Clone ZBX’s receiving wallet at zbx-exchanges.com.
• Forwarding-wallet pathway documented hop-by-hop with chain-of-custody hashes.
• Cross-chain bridge transactions where the operator routed value out of the deposit chain.
• Mixer or coin-join interactions, where applicable.
• Final off-ramp at a centralised exchange — the compliance counterparty named in the recovery filing.

Off-ramp map — where the funds left the chain:

• Off-ramp endpoint for Clone ZBX resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
• Clone ZBX’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
• The compliance packet for Clone ZBX is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
• If the Clone ZBX off-ramp counterparty does not respond inside the published window, escalation routes through IC3, state AG, and civil discovery.

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

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

What we read in a Clone ZBX casefile:

• Chains the Clone ZBX 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 Clone ZBX — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
• Filings the Clone ZBX 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:

• On the Clone ZBX casefile — never request a seed phrase. Ever.
• On the Clone ZBX casefile — never request remote-access logins to a wallet or exchange.
• On the Clone ZBX casefile — never demand an upfront cash retainer to scope the matter.
• On the Clone ZBX casefile — never promise a guaranteed recovery. The trail does not promise one.
• On the Clone ZBX casefile — never call the claimant unsolicited. Written-only.