The annotation reads, wallet trace:

• Deposit confirmations from the claimant to Apexforex Exchange’s receiving wallet at apexforexexchange.com.
• 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.

The annotation continues, off-ramp endpoint:

• Apexforex Exchange casefiles end at a centralised exchange, Bybit, KuCoin, OKX, or Gate.io are common; the casefile names the actual deposit address that received the consolidated funds.
• Off-ramp wallet for Apexforex Exchange is matched against compliance and chain-analytics datasets the Professor reads daily.
• Compliance leverage applied to the named off-ramp for Apexforex Exchange, the packet is delivered in compliance-desk format.
• Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the Apexforex Exchange casefile.

The Professor’s recovery note for Apexforex Exchange:

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