On-chain reading — wallet flow for CF Merchants:

• Deposit transaction hashes from the claimant wallet to the CF Merchants 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 — CF Merchants casefile:

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

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

1. Triage on CF Merchants — submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
2. Trace on CF Merchants — deposit pathway mapped across chains, captured with chain-of-custody hashes.
3. Identify on CF Merchants — off-ramp endpoint matched to a named exchange counterparty.
4. File the CF Merchants packet — IC3, state AG (where loss meets state thresholds), off-ramp compliance desk, and civil-discovery overlay where dollar value supports it.
5. Follow-through on CF Merchants — the Professor stays on the casefile until a documented next step exists.

What we read in a CF Merchants casefile:

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

Boundaries on every CF Merchants casefile — never crossed:

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