On-chain reading, wallet flow for CFDBUY:

• Deposit confirmations from the claimant to CFDBUY’s receiving wallet at cfdbuy.com.
• Forwarding-wallet pathway documented hop-by-hop with chain of custody hashes.
• Cross-chain bridge transactions where the operator routed value out of the deposit chain.
• Mixer or coin-join interactions, where applicable.
• Final off-ramp at a centralised exchange, the compliance counterparty named in the recovery filing.

The Professor’s off-ramp note:

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

How a CFDBUY casefile becomes a evidence filing:

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