The annotation reads, wallet trace:

• Claimant deposit hashes, provided in the case submission and verified against the public ledger for FORE XF.
• 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:

• Off-ramp endpoint for FORE XF resolves to a named centralised counterparty, the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
• FORE XF’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
• The compliance packet for FORE XF is structured the way an off-ramp compliance reviewer expects to receive evidence, header, hashes, narrative, ask.
• If the FORE XF off-ramp counterparty does not respond inside the published window, escalation routes through IC3, state AG, and civil discovery.

How a FORE XF casefile becomes a evidence filing:

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