On-chain reading, wallet flow for Kong Shing:

• Claimant-to-platform deposit transactions on the deposit chain used by Kong Shing.
• Operator-controlled forwarding wallets where deposits consolidate ahead of laundering or off-ramping.
• Cross-chain bridge events to chains with deeper exchange liquidity.
• Privacy-service interactions, where present in the trail.
• Off-ramp wallet, the named centralised-exchange endpoint.

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

• Kong Shing’s off-ramp endpoint, in this casefile, is the centralised exchange that holds compliance leverage, typically named in the packet alongside the deposit address.
• Chain-analytics datasets cross-reference the Kong Shing off-ramp wallet against historical laundering throughput.
• The Kong Shing packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
• Escalation pathways for Kong Shing, where needed: IC3, the relevant state AG, and a civil-discovery overlay for KYC on the off-ramp wallet.

Recovery pathway, how this casefile moves toward filing:

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

Reading-list, chains and exchanges in scope:

• Deposit-side chains in Kong Shing casefiles, typically the major chains (BTC, ETH) and the high-throughput stablecoin chains (Tron USDT, BSC USDT), with bridge crossings noted.
• Off-ramps named in Kong Shing packets, centralised exchanges that accept regulator-grade compliance filings.
• Filing options on Kong Shing, IC3 (US), state AG, off-ramp compliance desk, civil-discovery KYC where the dollar value warrants it.