From the marginalia, the deposit pathway:

• Deposit transaction hashes from the claimant wallet to the Mez Capital platform receiving address.
• Forwarding wallets the platform consolidated through, typically two to four hops on the deposit chain (BTC / ETH / USDT-TRC20 / BSC / Polygon / Arbitrum / Optimism / Avalanche).
• Bridge crossings between chains, where the operator moves value into a chain with deeper liquidity ahead of the off-ramp.
• Mixer interactions, Tornado-Cash variants, Sinbad, and the smaller obfuscation services that operators rotate through under regulatory pressure.
• Final off-ramp wallet, the centralised exchange deposit address that received the consolidated funds.

The Professor’s off-ramp note:

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

Recovery sequence, from on-chain reading to filed packet:

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