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

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

Recovery pathway, how this casefile moves toward filing:

1. Casefile review on BlueMartin, reading the submission against the no-go list.
2. Trace mapping on BlueMartin, pathway documented to chain of custody standard.
3. Off-ramp naming on BlueMartin, exchange endpoint identified.
4. Packet filing on BlueMartin, to the named off-ramp, IC3, state AG; civil discovery overlay as applicable.
5. Documented follow-through on BlueMartin.

Reading-list, chains and exchanges in scope:

• Deposit-side chains in BlueMartin 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 BlueMartin packets, centralised exchanges that accept regulator-grade compliance filings.
• Filing options on BlueMartin, IC3 (US), state AG, off-ramp compliance desk, civil-discovery KYC where the dollar value warrants it.

Boundaries on every BlueMartin casefile, never crossed:

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