The Professor’s off-ramp note:

• Endpoint counterparty in the BlumBerg casefile is named, typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• BlumBerg’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 BlumBerg packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the BlumBerg 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. Triage on BlumBerg, submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
2. Trace on BlumBerg, deposit pathway mapped across chains, captured with chain of custody hashes.
3. Identify on BlumBerg, off-ramp endpoint matched to a named exchange counterparty.
4. File the BlumBerg packet, IC3, state AG (where loss meets state thresholds), off-ramp compliance desk, and civil-discovery overlay where dollar value supports it.
5. Follow-through on BlumBerg, the Professor stays on the casefile until a documented next step exists.

Boundaries on every BlumBerg casefile, never crossed:

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