Reading the wallets, CBF Trade Services casefile:

• Claimant-to-platform deposit transactions on the deposit chain used by CBF Trade Services.
• Operator-controlled forwarding wallets where deposits consolidate ahead of laundering or off-ramping.
• Cross-chain bridge events to chains with deeper exchange liquidity.
• Privacy-service interactions, where present in the trail.
• Off-ramp wallet, the named centralised-exchange endpoint.

Off-ramp summary, CBF Trade Services casefile:

• CBF Trade Services off-ramps consistently to centralised exchanges, Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The CBF Trade Services off-ramp address is matched to known compliance feeds, the Professor’s standing dataset plus chain-analytics references.
• Compliance leverage is applied at the named counterparty for CBF Trade Services, the packet meets the off-ramp’s published compliance standard.
• When the CBF Trade Services off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

The Professor’s recovery note for CBF Trade Services:

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

Recovery scammers do these things; the Professor never does:

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