The annotation reads, wallet trace:

• Claimant-to-platform deposit transactions on the deposit chain used by Clone A. Eternity Capital Management.
• 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.

The annotation continues, off-ramp endpoint:

• Endpoint counterparty in the Clone A. Eternity Capital Management casefile is named, typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• Clone A. Eternity Capital Management’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 Clone A. Eternity Capital Management packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the Clone A. Eternity Capital Management 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 pathway, how this casefile moves toward filing:

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