The annotation reads, wallet trace:

• Claimant deposit hashes, provided in the case submission and verified against the public ledger for CAANHOLDINGS.
• Forwarding wallets on the deposit chain, each hop documented with the forwarding tx hash and the consolidating wallet.
• Bridge events into chains where the operator can off-ramp at scale.
• Mixer or privacy-service interactions, where present, listed with the contract address and the deposit/withdraw side.
• Off-ramp endpoint, the centralised exchange deposit address holding the compliance lever.

The annotation continues, off-ramp endpoint:

• Endpoint counterparty in the CAANHOLDINGS casefile is named, typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• CAANHOLDINGS’s off-ramp wallet is then matched against compliance feeds the Professor maintains a standing read on.
• Leverage is applied to that named counterparty, the CAANHOLDINGS packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the CAANHOLDINGS off-ramp is non-cooperative, the casefile escalates to IC3, the relevant state AG, and (where dollar value warrants) a civil-discovery overlay for KYC.

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

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