Wallet trace — what the Professor maps:

• Deposit transaction hashes from the claimant wallet to the BTL platform receiving address.
• Forwarding wallets the platform consolidated through — typically two to four hops on the deposit chain (BTC / ETH / USDT-TRC20 / BSC / Polygon / Arbitrum / Optimism / Avalanche).
• Bridge crossings between chains, where the operator moves value into a chain with deeper liquidity ahead of the off-ramp.
• Mixer interactions — Tornado-Cash variants, Sinbad, and the smaller obfuscation services that operators rotate through under regulatory pressure.
• Final off-ramp wallet — the centralised exchange deposit address that received the consolidated funds.

Off-ramp summary — BTL casefile:

• On the BTL 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 BTL is run against chain-analytics datasets and the Professor’s own compliance feeds.
• A regulator-ready packet is delivered to the named counterparty — the BTL casefile is built to the off-ramp’s compliance standard.
• Where the off-ramp will not engage, BTL escalates to IC3, state AG, and civil-discovery overlay.

Pathway to recovery — what happens after the trail is mapped:

1. Read the BTL submission — written go/no-go returned.
2. Map the BTL wallet trail — every hop captured with chain-of-custody hashes.
3. Name the BTL off-ramp — endpoint counterparty identified.
4. Build and file the BTL recovery packet — to IC3, state AG, off-ramp compliance, civil-discovery overlay.
5. Stay on the BTL file — until written next steps exist.

What the on-chain reading covers:

• Chains tracked on BTL — 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 BTL — named exchange counterparties with public compliance contacts.
• Filings supported on BTL — IC3, state AG, off-ramp compliance, civil discovery — selected by the dollar value and the off-ramp’s responsiveness.

Boundaries on every BTL casefile — never crossed:

• BTL policy — seed phrases are never requested.
• BTL policy — remote-access logins are never requested.
• BTL policy — no upfront cash retainer to scope.
• BTL policy — no guaranteed-recovery language. None.
• BTL policy — no unsolicited calls. The Professor responds in writing only.