The annotation reads, wallet trace:

• Initial deposit hashes to the GoldCapital24 receiving address at goldcapital24.com.
• Hop-by-hop forwarding wallets across the deposit chain, captured with chain of custody hashes.
• Cross-chain bridge events that move value into the chain where liquidity supports the eventual off-ramp.
• Obfuscation events through mixer contracts and privacy services.
• Centralised-exchange off-ramp wallets, the named counterparty that holds compliance leverage.

Off-ramp map, where the funds left the chain:

• Endpoint counterparty in the GoldCapital24 casefile is named, typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• GoldCapital24’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 GoldCapital24 packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the GoldCapital24 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. Read the GoldCapital24 submission, written go/no-go returned.
2. Map the GoldCapital24 wallet trail, every hop captured with chain of custody hashes.
3. Name the GoldCapital24 off-ramp, endpoint counterparty identified.
4. Build and file the GoldCapital24 recovery packet, to IC3, state AG, off-ramp compliance, civil-discovery overlay.
5. Stay on the GoldCapital24 file, until written next steps exist.