The annotation reads — wallet trace:

• Deposit transaction hashes from the claimant wallet to the Pipspool platform receiving address.
• Forwarding wallets the platform consolidated through — typically two to four hops on the deposit chain (BTC / ETH / USDT-TRC20 / BSC / Polygon / Arbitrum / Optimism / Avalanche).
• Bridge crossings between chains, where the operator moves value into a chain with deeper liquidity ahead of the off-ramp.
• Mixer interactions — Tornado-Cash variants, Sinbad, and the smaller obfuscation services that operators rotate through under regulatory pressure.
• Final off-ramp wallet — the centralised exchange deposit address that received the consolidated funds.

Off-ramp map — where the funds left the chain:

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

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

What the casefile records — chains and counterparties:

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

What is never asked of a claimant:

• Hard line on Pipspool — no seed-phrase requests, period.
• Hard line on Pipspool — no remote logins requested.
• Hard line on Pipspool — no upfront cash retainer.
• Hard line on Pipspool — no guarantee language.
• Hard line on Pipspool — no unsolicited phone outreach.