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

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

The Professor’s recovery note for DSG:

1. Casefile triage on DSG, the submission is read; a written assessment is delivered.
2. Forensic trace on DSG, every hop in the deposit pathway is captured and hashed.
3. Off-ramp identification, the DSG endpoint is named.
4. Recovery filing on DSG, packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
5. Continuing review of DSG, the Professor follows the casefile until next-step documentation exists.

What we read in a DSG casefile:

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

What the Professor will never do, by policy:

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