The annotation reads, wallet trace:

• Deposit-side hashes from claimant wallets into CCXTrade’s receiving addresses.
• Operator forwarding wallets, deposit consolidation documented to chain of custody standards.
• Inter-chain bridge transactions when value moves toward off-ramp liquidity.
• Mixer/obfuscation events the operator routed through, where present.
• Final off-ramp endpoint and named counterparty exchange.

The annotation continues, off-ramp endpoint:

• CCXTrade off-ramps consistently to centralised exchanges, Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The CCXTrade 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 CCXTrade, the packet meets the off-ramp’s published compliance standard.
• When the CCXTrade off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

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

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