Wallet trace — what the Professor maps:

• Deposit transaction hashes from the claimant wallet to the Halebore 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 reading — exchange counterparty for Halebore:

• Halebore casefiles end at a centralised exchange — Bybit, KuCoin, OKX, or Gate.io are common; the casefile names the actual deposit address that received the consolidated funds.
• Off-ramp wallet for Halebore is matched against compliance and chain-analytics datasets the Professor reads daily.
• Compliance leverage applied to the named off-ramp for Halebore — the packet is delivered in compliance-desk format.
• Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the Halebore casefile.

Recovery sequence — from on-chain reading to filed packet:

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

What the on-chain reading covers:

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

What the Professor will never do — by policy:

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