Reading the wallets, Exbina casefile:

• Initial deposit hashes to the Exbina receiving address at exbina.com.
• Hop-by-hop forwarding wallets across the deposit chain, captured with chain of custody hashes.
• Cross-chain bridge events that move value into the chain where liquidity supports the eventual off-ramp.
• Obfuscation events through mixer contracts and privacy services.
• Centralised-exchange off-ramp wallets, the named counterparty that holds compliance leverage.

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

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

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

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

What the Professor will never do, by policy:

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