From the marginalia, the deposit pathway:

• Deposit-side hashes from claimant wallets into 2B FX’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 2B FX:

• 2B FX’s off-ramp endpoint, in this casefile, is the centralised exchange that holds compliance leverage, typically named in the packet alongside the deposit address.
• Chain-analytics datasets cross-reference the 2B FX off-ramp wallet against historical laundering throughput.
• The 2B FX packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
• Escalation pathways for 2B FX, where needed: IC3, the relevant state AG, and a civil-discovery overlay for KYC on the off-ramp wallet.

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

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

Lines the Professor will not cross:

• Boundary on 2B FX, seed phrases are off-limits.
• Boundary on 2B FX, remote logins are off-limits.
• Boundary on 2B FX, upfront cash retainers are off-limits.
• Boundary on 2B FX, guaranteed-recovery promises are off-limits.
• Boundary on 2B FX, unsolicited outbound contact is off-limits.