The annotation reads — wallet trace:

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

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

1. Triage on Connected Pips — submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
2. Trace on Connected Pips — deposit pathway mapped across chains, captured with chain-of-custody hashes.
3. Identify on Connected Pips — off-ramp endpoint matched to a named exchange counterparty.
4. File the Connected Pips 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 Connected Pips — the Professor stays on the casefile until a documented next step exists.

Chains and off-ramps the Professor follows:

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

Lines the Professor will not cross:

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