Reading the wallets, Market Z casefile:

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

The Professor’s off-ramp note:

• Market Z’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 Market Z off-ramp wallet against historical laundering throughput.
• The Market Z packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
• Escalation pathways for Market Z, where needed: IC3, the relevant state AG, and a civil-discovery overlay for KYC on the off-ramp wallet.

How a Market Z casefile becomes a evidence filing:

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