From the marginalia, the deposit pathway:

• Deposit-side hashes from claimant wallets into DC Markets’s receiving addresses.
• Operator forwarding wallets, deposit consolidation documented to chain of custody standards.
• Inter-chain bridge transactions when value moves toward off-ramp liquidity.
• Mixer/obfuscation events the operator routed through, where present.
• Final off-ramp endpoint and named counterparty exchange.

Off-ramp reading, exchange counterparty for DC Markets:

• DC Markets off-ramps consistently to centralised exchanges, Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The DC Markets off-ramp address is matched to known compliance feeds, the Professor’s standing dataset plus chain-analytics references.
• Compliance leverage is applied at the named counterparty for DC Markets, the packet meets the off-ramp’s published compliance standard.
• When the DC Markets off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

How a DC Markets casefile becomes a evidence filing:

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

What the Professor will never do, by policy:

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