Wallet trace — what the Professor maps:

• Deposit transaction hashes from the claimant wallet to the MintCFD 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.

The Professor’s off-ramp note:

• Off-ramp endpoint for MintCFD resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
• MintCFD’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
• The compliance packet for MintCFD is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
• If the MintCFD off-ramp counterparty does not respond inside the published window, escalation routes through IC3, state AG, and civil discovery.

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

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

What the on-chain reading covers:

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

Boundaries on every MintCFD casefile — never crossed:

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