Reading the wallets, BitExpat casefile:

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

• BitExpat off-ramps consistently to centralised exchanges, Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The BitExpat off-ramp address is matched to known compliance feeds, the Professor’s standing dataset plus chain-analytics references.
• Compliance leverage is applied at the named counterparty for BitExpat, the packet meets the off-ramp’s published compliance standard.
• When the BitExpat off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

How a BitExpat casefile becomes a evidence filing:

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