Reading the wallets, RBG Markets casefile:

• Deposit-side hashes from claimant wallets into RBG Markets’s receiving addresses.
• Operator forwarding wallets, deposit consolidation documented to chain of custody standards.
• Inter-chain bridge transactions when value moves toward off-ramp liquidity.
• Mixer/obfuscation events the operator routed through, where present.
• Final off-ramp endpoint and named counterparty exchange.

Off-ramp reading, exchange counterparty for RBG Markets:

• Endpoint counterparty in the RBG Markets casefile is named, typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• RBG Markets’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 RBG Markets packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the RBG Markets 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, RBG Markets casefile reviewed against the no-go list, written reply within one business day.
2. Pathway trace, RBG Markets deposit and forwarding wallets captured.
3. Endpoint identification, RBG Markets off-ramp wallet named.
4. Filing, RBG Markets packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
5. Ongoing follow, RBG Markets stays on file until a documented next step is reached.

Lines the Professor will not cross:

• What the Professor will not do on RBG Markets, ask for a seed phrase.
• What the Professor will not do on RBG Markets, request remote-access logins.
• What the Professor will not do on RBG Markets, demand cash up front.
• What the Professor will not do on RBG Markets, promise a guarantee.
• What the Professor will not do on RBG Markets, call you out of the blue.