Reading the wallets, YorkBit casefile:

• Initial deposit hashes to the YorkBit receiving address at yorkbit.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 reading, exchange counterparty for YorkBit:

• On the YorkBit casefile, the off-ramp endpoint resolves to a centralised exchange, Bitfinex, MEXC, or Crypto.com seen often in this segment, with the larger venues routed through under stress.
• The off-ramp wallet for YorkBit is run against chain-analytics datasets and the Professor’s own compliance feeds.
• A evidence packet is delivered to the named counterparty, the YorkBit casefile is built to the off-ramp’s compliance standard.
• Where the off-ramp will not engage, YorkBit escalates to IC3, state AG, and civil-discovery overlay.

Recovery pathway, how this casefile moves toward filing:

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

Chains and off-ramps the Professor follows:

• Chains tracked on YorkBit, Bitcoin and Ethereum at the deposit side; Tron USDT-TRC20 and BSC at the consolidation side; bridges crossed where the operator chases liquidity.
• Off-ramps tracked on YorkBit, named exchange counterparties with public compliance contacts.
• Filings supported on YorkBit, IC3, state AG, off-ramp compliance, civil discovery, selected by the dollar value and the off-ramp’s responsiveness.