On-chain reading, wallet flow for WhiteBull:

• Claimant-to-platform deposit transactions on the deposit chain used by WhiteBull.
• Operator-controlled forwarding wallets where deposits consolidate ahead of laundering or off-ramping.
• Cross-chain bridge events to chains with deeper exchange liquidity.
• Privacy-service interactions, where present in the trail.
• Off-ramp wallet, the named centralised-exchange endpoint.

The Professor’s off-ramp note:

• Off-ramp endpoint for WhiteBull resolves to a named centralised counterparty, the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
• WhiteBull’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
• The compliance packet for WhiteBull is structured the way an off-ramp compliance reviewer expects to receive evidence, header, hashes, narrative, ask.
• If the WhiteBull off-ramp counterparty does not respond inside the published window, escalation routes through IC3, state AG, and civil discovery.

Recovery pathway, how this casefile moves toward filing:

1. Read the WhiteBull submission, written go/no-go returned.
2. Map the WhiteBull wallet trail, every hop captured with chain of custody hashes.
3. Name the WhiteBull off-ramp, endpoint counterparty identified.
4. Build and file the WhiteBull recovery packet, to IC3, state AG, off-ramp compliance, civil-discovery overlay.
5. Stay on the WhiteBull file, until written next steps exist.

What the casefile records, chains and counterparties:

• Deposit-side chains in WhiteBull casefiles, typically the major chains (BTC, ETH) and the high-throughput stablecoin chains (Tron USDT, BSC USDT), with bridge crossings noted.
• Off-ramps named in WhiteBull packets, centralised exchanges that accept regulator-grade compliance filings.
• Filing options on WhiteBull, IC3 (US), state AG, off-ramp compliance desk, civil-discovery KYC where the dollar value warrants it.