The Professor’s off-ramp note:

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

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

Chains and off-ramps the Professor follows:

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

Boundaries on every CBD casefile, never crossed:

• CBD policy, seed phrases are never requested.
• CBD policy, remote-access logins are never requested.
• CBD policy, no upfront cash retainer to scope.
• CBD policy, no guaranteed-recovery language. None.
• CBD policy, no unsolicited calls. The Professor responds in writing only.