The annotation reads, wallet trace:

• Deposit confirmations from the claimant to 24 CFDCAP’s receiving wallet at 24cfdcap.net.
• 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.

How a 24 CFDCAP casefile becomes a evidence filing:

1. Casefile triage on 24 CFDCAP, the submission is read; a written assessment is delivered.
2. Forensic trace on 24 CFDCAP, every hop in the deposit pathway is captured and hashed.
3. Off-ramp identification, the 24 CFDCAP endpoint is named.
4. Recovery filing on 24 CFDCAP, packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
5. Continuing review of 24 CFDCAP, the Professor follows the casefile until next-step documentation exists.

What the casefile records, chains and counterparties:

• Deposit-side chains in 24 CFDCAP casefiles, typically the major chains (BTC, ETH) and the high-throughput stablecoin chains (Tron USDT, BSC USDT), with bridge crossings noted.
• Off-ramps named in 24 CFDCAP packets, centralised exchanges that accept regulator-grade compliance filings.
• Filing options on 24 CFDCAP, IC3 (US), state AG, off-ramp compliance desk, civil-discovery KYC where the dollar value warrants it.

Lines the Professor will not cross:

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