From the marginalia — the deposit pathway:

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

• Endpoint counterparty in the GatesBridge casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• GatesBridge’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 GatesBridge packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the GatesBridge 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.

How a GatesBridge casefile becomes a regulator-ready filing:

1. Casefile review on GatesBridge — reading the submission against the no-go list.
2. Trace mapping on GatesBridge — pathway documented to chain-of-custody standard.
3. Off-ramp naming on GatesBridge — exchange endpoint identified.
4. Packet filing on GatesBridge — to the named off-ramp, IC3, state AG; civil discovery overlay as applicable.
5. Documented follow-through on GatesBridge.

What the on-chain reading covers:

• Chains in scope for GatesBridge — the chains that handle the volume of casefile activity in this segment (BTC, ETH, Tron, BSC, plus L2s).
• Off-ramps in scope for GatesBridge — named centralised exchanges with compliance leverage.
• Filings supported on GatesBridge — IC3, state AG, off-ramp desk, civil discovery as applicable.

What the Professor will never do — by policy:

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