Off-ramp reading, exchange counterparty for Schatz:

• Endpoint counterparty in the Schatz casefile is named, typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• Schatz’s off-ramp wallet is then matched against compliance feeds the Professor maintains a standing read on.
• Leverage is applied to that named counterparty, the Schatz packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the Schatz off-ramp is non-cooperative, the casefile escalates to IC3, the relevant state AG, and (where dollar value warrants) a civil-discovery overlay for KYC.

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

1. Submission triage, Schatz casefile reviewed against the no-go list, written reply within one business day.
2. Pathway trace, Schatz deposit and forwarding wallets captured.
3. Endpoint identification, Schatz off-ramp wallet named.
4. Filing, Schatz packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
5. Ongoing follow, Schatz stays on file until a documented next step is reached.

What the casefile records, chains and counterparties:

• Deposit + forwarding chains for Schatz, Bitcoin, Ethereum, Tron USDT-TRC20, plus the smart-contract chains (BSC, Polygon, Avalanche, Arbitrum, Optimism) that cross via bridges.
• Off-ramps the Schatz casefile may resolve to, centralised exchanges that respond to compliance filings.
• Filing pathways on Schatz, IC3, state AG, off-ramp compliance, and civil-discovery overlay.

What the Professor will never do, by policy:

• On the Schatz casefile, never request a seed phrase. Ever.
• On the Schatz casefile, never request remote-access logins to a wallet or exchange.
• On the Schatz casefile, never demand an upfront cash retainer to scope the matter.
• On the Schatz casefile, never promise a guaranteed recovery. The trail does not promise one.
• On the Schatz casefile, never call the claimant unsolicited. Written-only.