The annotation reads — wallet trace:

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

The Professor’s off-ramp note:

• HubbleBIT 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 HubbleBIT is matched against compliance and chain-analytics datasets the Professor reads daily.
• Compliance leverage applied to the named off-ramp for HubbleBIT — the packet is delivered in compliance-desk format.
• Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the HubbleBIT casefile.

Filing pathway — the next step after the off-ramp is identified:

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

Reading-list — chains and exchanges in scope:

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

Lines we never cross — by published policy:

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