On-chain reading, wallet flow for UOSHING:

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

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

Recovery pathway, how this casefile moves toward filing:

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

What the casefile records, chains and counterparties:

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