Reading the wallets, Vault Markets casefile:

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

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

Recovery pathway, how this casefile moves toward filing:

1. First read on Vault Markets, incoming submission is reviewed against the no-go list and a written go/no-go is returned in writing.
2. Wallet trace on Vault Markets, deposit-to-off-ramp pathway is mapped across chains with verifiable hashes.
3. Counterparty identification, the off-ramp endpoint for Vault Markets is named to a centralised exchange wallet.
4. Packet filing on Vault Markets, IC3, state AG, off-ramp compliance desk; civil discovery if dollar value justifies it.
5. Casefile follow-through, the Professor stays with Vault Markets until a documented outcome or escalation step is on file.